Windows 10: Anniversary update killed my laptop

Hi guys

Comin over from seven forums *Smile

After a recent update, i shut down my notebook. Next time I turned it on it got suck right after POST, so all I see is a blank screen. This happens before windows even begins to load, it's basically a DOS style blank screen with a blinking "_" sign and nothing is happening.

I tried to fix it using the repair function from the recovery USB stick, but it didn't work. I also tried repairing the boot sector because windows is still there but it's just not booting.
I tried all the commands from https://support.microsoft.com/en-us/kb/927392. Sadly, no success. I also ran the hardware check and all is fine, it's definitely a software related problem.

Interestingly, while dabbling with the bootloader i discovered that for some reason the windows partition letter has changed to letter H: (from standard C: ). I managed to change it back to C: and make the windows partition the active partition, but still nothing.

Btw I have an upgrade version, coming from Windows 7.

Any ideas on how I can fix my windows without formatting/reinstalling the whole system? All files are there and I can access the folders via command line through recovery USB stick, and I see the windows and windows.old folders.
Thanks!

Edit:
I have 2 HDDs, 1 with system (256gb SSD) and 1 standard HDD for files.

:)

 

windows 10 creator's update problem

Wayne, it was truly hung up. I was able to get the advanced options menu to come up and ended up having to reset my PC... not happy but at least its not dead. The Windows 10 Anniversary update killed my laptop!

Thanks again for your help.

Audrey

 

Logitech QuickCam Pro 9000 killed by Win 10 Anniv. Update

Windows 10 Anniversary update killed my Logitech QuickCam Pro 9000 camera, specifically, Launcher_Main.exe, both in a Recovery Drive reinstall of Win 10 on my desktop and on my laptop that only received the anniv. update when I booted it up this morning.
Perhaps someone knows of a workaround, like running it in compatibility mode for Millennium Edition?

 

OK I now see that drive letters are all over the place. The partition with Windows is apparently now listed as F: rather than C: :/

 

Can you do the following again?

 

I found the following:
"Windows Recovery Environment mode is operating system independent recovery tool to repair the operating system files. When you use diskpart from WinRE mode, the system reserved partition is considered as C and the windows partition will be the next drive letter after C." (http://answers.microsoft.com/en-us/w...6-df6d07cb0b2c)

So I`m not sure if my windows partition really should be C:

C: is currently names "system reserved" and is empty, and I also see a BOOT (X*Smile drive, while my windows instalaltion is on F:

Wtf? *Sad

 

Will it boot a DVD or USB ? if so try Macrium Reflects Rescue CD and the "Fix windows Boot Problems" Option

Macrium is also on Kyhi's Bootdisk........... available here on Ten Forums . i use the 160707 version

Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 Forums

 

That fixed it!!!!
Somehow the update messed up my boot partition. Ultimately, I deleted the "System reserved" partition (it was 100mb and empty anyhow) which assigned my primary system drive back to "C:".
Now I still couldn't fix the problem with Missing Boot Manager via command line (using bootrec.exe commands).
I downloaded Kyhis Bootdisk and hit the Fix boot problems thing.
After hours of dabbling around, my notebook is booting again!

Many thanks, I was not aware of this tool *Smile

Cheers and enjoy your weekend!

 

Glad you are back up and Running , another useful Tool is MiniTool Partition Wizard 9 (Free) , perhaps install it and post a Pic of the Partitions it now sees ..... it should not have been necessary to delete the system reserved partition ...it is needed.... , ( it's not empty ) but in an upgrade scenario you end up with multiple Recovery Partitions etc as Win10 makes it's own new ones.

this is my standard Basic GPT SSD Disk in Win10 (Disk 1) as you can see there is an extra Recovery Partition on the End which I have now removed actually.

450mb
100mb
16mb
XXXGB

The above is standard for a Clean Win10 Install. you can right click a partition and "Explore" it and see they are not empty, this is something Disk Management and File Explorer can't do. DM does not even see the MSR (Other) partition in fact.

 

According to what I read it's not required since only bootloader is on it ans some stuff in case you wanna encript your hard drive later on, which I don't want. Since my bootlaoder was ****ed anyhow, I just put it on the same partition as my Windows folder.

This is how it looks now

 

For some reason your Pic does not show a larger image if clicked on, so I can't really see what the layout is but I suspect you have a MBR Disk not GPT since you came from Win7 .

Where no System Partition (EFI) is found , Windows 10 will make a Folder on C: instead and place the boot files there , it is needed , it won't boot without the Boot files as you already found out....

It seems it has worked out ok though , and you can always change the Disk to GPT when you Clean install Win10 at some point.


KB.

 

Last week I clean-installed 1607 on an MBR disk. The 500 MB space is the system reserved partition.

I guess your problem would not have arisen if you had clean-installed Windows 10 instead of upgrading.

 

If you don't "clean" the Disk (delete all partitions) before Clean Installing Win10 on GPT or MBR Disks it will reuse existing partitions (and add some possibly) , as it appears it has on your's Matthew . If there is no System Partition like if Win7 , was on the Disk 1st, Win10 will put the Boot files in the C:\EFI Folder instead (perhaps C:\boot? I don't have MBR now to check)

If the recovery Partition is empty , then the recovery files may also be on C:\ ..... in C:\Windows\Recovery

Minitool Partition Wizard makes things easy to see and you can "explore" partition that windows won't let you view normally as well. You can use the Portable version if you don't want to install it (or get Loader.exe errors)

KB

 

second try *Smile

 

Better *Smile

Both drives look like you deleted the Win7 system partitions off at some point ? both have 100mb unallocated at the front end. Not sure why one is set as logical (normally Primary unless more that 4 partition) , not sure why the 2nd one is set to dynamic either ?

Even on MBR disk's the Recovery Partition is Usually the 1st partition but if Win10 finds one too small it will add one to the End with the latest Recovery Files for the Win10 Version you are installing.

Maybe time for a House Cleaning *Smile

I ran into an issue with Win10 AU and my MBR disk back in Aug. it would not install on an MBR Disk I had upgraded from win7 this post shows what I did to fix that and convert my Drives to GPT at the same time

https://www.tenforums.com/installatio...-mbr-disk.html


the short version I posted in another Thread today

Did Windows Give UP on the Win 10 Anniversary Update?