In case your Windows shatters.

AlienALX

Well-known member
OK so I guess you guys have all seen the latest Windows update (the big one) and have installed it. However, though quite rare, this can cause big issues. Now oddly enough it all went fine on my rig at my mother's, so when it chose to install on Sunday I deleted the rollback file as I figured all would be well. It wasn't. All of a sudden I had a 500mb hard drive, letter M: (yours will vary) and Windows was continually whining that it was full and flashing messages at me.

This is not the first time Windows has busted my PC with an update and I am sure it won't be the last but if this happens to you (and you sprout a new 500mb hard drive that won't go away) then this is the fix.

open cmd (type CMD in the "Type here to search" box)
type diskpart (this will open diskpart)
new window, type list volume (only type list volume)
find the volume in question which might be volume 0 (mine was Volume 10)
then type select volume 0 (or whatever volume its assigned)
and then type remove letter C (mine was M).

This will make the new hard drive go away and stop Windows whining. It is obviously some sort of boot area that Windows usually hides, but this update can make it pop up and start complaining about low disk space.
 
Thanks mate. My old mans PC has gone cactus and of course he 'didn't see any error or do anything and certainly didn't just start clicking random buttons and stuff'

Maybe this could be the culprit. I have to go have a look tomorrow so I'll keep this info handy!
 
Glad it helped. It seems quite rare, and probably because I have loads of hard drives and partitions, but yeah it's a royal PITA. I've known how to make hard drives appear for many years now, but had never learned the art of hiding one lol.
 
My update went ok other than totally borking my grub forcing me to boot to usb to fix that when I eventually get round it
 
My update went ok other than totally borking my grub forcing me to boot to usb to fix that when I eventually get round it

Yeah it is playing with partitions for some reason. I have a lot of drives (you can tell by it being device 10 and given the letter M: lol) so I would imagine that is the cause of it.

Usually when I install I remove all of my drives to stop Windows spreading onto them. I have had it put the bloody boot sector on my 2tb storage drive before ffs.
 
Back
Top