- Jun 27, 2016
- 4
- 0
- 1,510
As what seems to be the result of trying to shrink my C: partition from around 1TB in order to create 256 GB of free space for a Linux installation, whilst telling me that I had 450 GB of space available for partitioning yet seemingly encountering an error after telling me there wasn't enough disk space after 15 minutes of waiting.
This is where the stupid comes in. After being told that there "wasn't enough free space," I decided to use a partition manager that I had used successfully in the past, AOMEI Partition Assistant. It let me resize my drive to make room for the desired free space, and rebooted into it's PreBoot thing where it took about 30 minutes to repartition my drive.
I have a spare Windows 10 USB installer lying around, and as I am unable to boot into Safe Mode, I used it to access a command prompt in which SFC /scannow does nothing and encounters 1 of two errors depending on how I use it. One being the service not running and two being that it wasn't able to do anything.
Upon running chkdsk, it came back with a 30-second list of a whole bunch of drive/sectors out not referencing things correctly.
This was fixed by running chkdsk /f and chkdsk /r.
The contents of the drive are intact; I can see them with the "dir" command as well as with mounting it on a LiveCD. It just sits at the windows logo with the spinning circle and the BSOD.
I read somewhere that it might be repairable with DISM, but I don't know how to do that from a Windows USB using offline instead of online.
**I tried the windows auto repair as the very first thing and it said that it couldn't do anything.
This is where the stupid comes in. After being told that there "wasn't enough free space," I decided to use a partition manager that I had used successfully in the past, AOMEI Partition Assistant. It let me resize my drive to make room for the desired free space, and rebooted into it's PreBoot thing where it took about 30 minutes to repartition my drive.
I have a spare Windows 10 USB installer lying around, and as I am unable to boot into Safe Mode, I used it to access a command prompt in which SFC /scannow does nothing and encounters 1 of two errors depending on how I use it. One being the service not running and two being that it wasn't able to do anything.
Upon running chkdsk, it came back with a 30-second list of a whole bunch of drive/sectors out not referencing things correctly.
This was fixed by running chkdsk /f and chkdsk /r.
The contents of the drive are intact; I can see them with the "dir" command as well as with mounting it on a LiveCD. It just sits at the windows logo with the spinning circle and the BSOD.
I read somewhere that it might be repairable with DISM, but I don't know how to do that from a Windows USB using offline instead of online.
**I tried the windows auto repair as the very first thing and it said that it couldn't do anything.
Facebook
Twitter
Instagram