@JoeyLópez the only realiable way is within Windows, which only lets you shrink down as far as the last written block (usually halfway on a new partition, could be later if the drive was used for a while)
Apart from that, gparted usually works. I've also used Acronis before.
I'm trying to shrink it, so I can make a new partition, move my ridiculously huge documents/pictures/other folders to it, shrink it again, and move it to the SSD, leaving my documents and such behind
Windows 10 and resizing partitions apparently don't mix.
I needed to migrate a partition to a smaller SSD, as outlined in this post, so in an attempt to move my massive documents folder to a place where it will remain on the HDD, I tried to shrink my main partition, as it had 120 GB of free space...
112 GB just from my documents folder alone... you see, I'm careless and probably have a few copies of massive files when I only need 1, and cleanup is rather daunting at that size
@JoeyLópez You say you have a Windows 10 installer handy. Do you know when that was created, and/or if it's the same version as is currently installed on the machine?
oh and I find it ironic that having stuff like system restore points makes it impossible to shrink partitions, as disabling it means it's not there to help when things go wrong
The EFI on a modern Mac can connect to the Internet, automatically download an install image for you and seamlessly do an in-place upgrade/reinstall while preserving your data/applications. All autonomously without booting to the OS if the OS can't boot.
On the off chance its doing something stupid like booting to the wrong BCD entry... Follow Bob's BCD Edit line of thought too. Basically, listen to Bob. Bob's smart.
Windows Resources Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios. The system file repair changes will take effect after the next reboot.
ok I did yes, I ran ren about four times and it still asked that
Narrator.exe.bak must already be there from before
making the command fail, but I still should have that file so I should be ok, right?
dism is also painfully slow
even shows tenths of a percent to show you how slowly it's running
might leave this one overnight, probably won't have time to return to the laptop until the evening. Maybe I could snap an image of the output (if I remember to) on my way out and send it later, I'll have the Chromebook all day