Win10 update, now can't boot...

paperfist

Diamond Member
Nov 30, 2000
6,539
286
126
www.the-teh.com
I've been running 10 for months with no issues. Tonight it kept asking me when I wanted to reboot to update. I ignored it and went to work. When I got back the computer rebooted and left me with an error: An operating system was not found.

I'm not sure if the SSD bit the bullet or the patch caused an issues. I check in BIOS to see what drive it was booting from (there's another drive with an old Win10 install) and for whatever reason it looked like the settings somehow changed to boot from the old SSD.

I tried to do a start up repair and that didn't work. Does anyone have any suggestions please?
 

mikeymikec

Lifer
May 19, 2011
19,926
14,170
136
Presumably you've booted from Win10 setup media in order to do the startup repair? A couple of things might be worth doing: Posting the results of the automatic repair (not necessarily word for word, but any checks ending in failure), and having a poke around with the DISKPART command (is it diskpart that allows one to look at partition configurations and what's set as active etc?).

If you did a UEFI install, I'd check the BIOS that UEFI is still enabled. Doing startup repairs when Windows is set to one configuration and the BIOS is set to the other is just a waste of time and it won't tell you what ought to be obvious to an effective boot troubleshooting program.
 
  • Like
Reactions: paperfist

deustroop

Golden Member
Dec 12, 2010
1,915
354
136
From the boot menu you could normally chose the boot disk. Are you unable to boot either disk ?
 
  • Like
Reactions: paperfist

paperfist

Diamond Member
Nov 30, 2000
6,539
286
126
www.the-teh.com
When you did the 950 install, was the old drive plugged in at the time?

No. Unplugged during the Win10 install. Plugged it back in afterwards.

Presumably you've booted from Win10 setup media in order to do the startup repair? A couple of things might be worth doing: Posting the results of the automatic repair (not necessarily word for word, but any checks ending in failure), and having a poke around with the DISKPART command (is it diskpart that allows one to look at partition configurations and what's set as active etc?).

If you did a UEFI install, I'd check the BIOS that UEFI is still enabled. Doing startup repairs when Windows is set to one configuration and the BIOS is set to the other is just a waste of time and it won't tell you what ought to be obvious to an effective boot troubleshooting program.

Yes, I did the setup media off a USB stick. I did automatic repair and I think the results were that it cannot be repaired.

I got into system restore and there seems to be a point created before the Windows critical update was applied. For some reason it won't let me select the drive to continue with the rollback.

I'll try doing DISKPART.

Interesting in BIOS I can select the Samsung 950 drive to boot from, however I was just looking at other settings and that drive doesn't show up under discovery like the 850 (It's actually a Samsung 830).

It's been a while since I did this install, I'm not sure if I went with UEFI.

From the boot menu you could normally chose the boot disk. Are you unable to boot either disk ?

I can boot from the Samsung 830 drive and that's what I'm using now. The Samsung 950 is the one I've been using all along and is the one that won't boot and gives the error that an OS cannot be found.

----

I'm going to try disconnecting the 830 drive to see if I can get a repair or restore to work on the 950 drive.

Thanks for the help guys!
 
Last edited:

paperfist

Diamond Member
Nov 30, 2000
6,539
286
126
www.the-teh.com
Well to clarify I'm using a Samsung 950 Pro m.2 on a ASUS Expansion card m.2 to mini SAS so I guess something could be wrong with that too! Though I just updated the firmware on this drive without a problem and can access the files as a slave drive...

DISKPART when just the above drive is hooked up says:

Volume 0 - C - Volume - NTFS - Partition - 476 GB - Healthy

From the file: Startup Repair diagnosis and repair log

Root cause found:
---------------------------
A recently serviced boot binary is corrupt.

And then in another session: (after I got startup repair to actually check the drive)
Root cause found:
---------------------------
A recently serviced boot binary is corrupt.

Repair action: Abort pending update installations
Result: Failed. Error code = 0x82f
Time taken = 813 ms
 

bruceb

Diamond Member
Aug 20, 2004
8,874
111
106
See this link for information .. you may need to use the method near the bottom ... you need to rebuild the bootrec ... Edit: Be sure nothing is in the USB Ports and see if Secure Boot is Disabled

http://www.pcworld.com/article/3113...ster-boot-record-and-fix-your-bricked-pc.html

Also try this from the Microsoft community:

Please follow these steps to boot into Recovery Environment and try to rebuild BCD.

a. Boot into Windows Recovery Environment using the Windows 10 USB or DVD.
b. Click on Repair your computer.

c. Click on Troubleshoot and in the Advanced options.
d. Select Command Prompt. Type the following commands into the prompt and press Enter key after each command.

bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
 
Last edited:
  • Like
Reactions: paperfist

paperfist

Diamond Member
Nov 30, 2000
6,539
286
126
www.the-teh.com
See this link for information .. you may need to use the method near the bottom ... you need to rebuild the bootrec
http://www.pcworld.com/article/3113...ster-boot-record-and-fix-your-bricked-pc.html

Thanks, will try later need to get to work.

So Windows update is the likely culprit for this corruption? I noticed the way it was trying to deploy the patch was different than what I am used to seeing where you could just delay it till later. This one seemed to want to do it now or force me to schedule it. I wasn't entirely sure if it was a virus in disguise or just a new version of Win update.
 

mikeymikec

Lifer
May 19, 2011
19,926
14,170
136
While at a recovery console I'd probably run the boot drive through a full chkdsk (/f /v /r) for the sake of getting it out of the way. I'm surprised that if it's saying a recently serviced binary is the problem then surely it should be able to roll back with system restore or whatever.

Other than that I'd google the error message and code and see if any interesting suggestions come up.
 
  • Like
Reactions: paperfist

paperfist

Diamond Member
Nov 30, 2000
6,539
286
126
www.the-teh.com
While at a recovery console I'd probably run the boot drive through a full chkdsk (/f /v /r) for the sake of getting it out of the way. I'm surprised that if it's saying a recently serviced binary is the problem then surely it should be able to roll back with system restore or whatever.

Other than that I'd google the error message and code and see if any interesting suggestions come up.

What's bizarre is since I disconnected the other drives the restore point is no longer available. Not much success searching that error specifically, but I'll redo the search.
 

deustroop

Golden Member
Dec 12, 2010
1,915
354
136
The update may have been the anniversary upgrade to ver 1607 which can cause an issue where there are more than one ssd boot drives on a system. The approach bruceb gave and my suggestion re SFC are the usual ways to repair a corrupted boot process. If they do not help, then just grab what you can from the 950 and reinstall windows using an updated iso. You apparently may d/l one from this site
http://windowsiso.net/windows-10-iso/windows-10-creators-update-1703-download-build-15063/.
Or clone the old drive but be careful when the AU comes along to disconnect all other boot drives when it asks to restart.
 

paperfist

Diamond Member
Nov 30, 2000
6,539
286
126
www.the-teh.com
Thanks for the help everyone.

I tried all the suggestions and while no errors, corruption or problems turned up I still cannot boot.

It's really odd that when I hook up the 830 drive system restore provides me with a restore point for the time that Windows did the critical update, but it will not let me deploy the restore point saying I need to enable system restore.

I've been trying to turn it on with a system prompt but nothing has worked.

Somehow, someway when I installed Win10 the 2 drives became linked together.
 

paperfist

Diamond Member
Nov 30, 2000
6,539
286
126
www.the-teh.com
Thanks Bruce I'll try that.

The weirdness continues, now I have a dual boot option of Windows 10 or Windows 10 Pro (the non booting one) on start up.

Off hand does anyone know if I can just copy the boot block stuff from the version that works to the one that doesn't?
 

paperfist

Diamond Member
Nov 30, 2000
6,539
286
126
www.the-teh.com

This is quite a command with loads of parameters! Dumb question time, what's (default) the Windows location?

EDIT: n/m I see I need to create another USB tool for this and not the recovery one.
  • bcdedit /set {default} bootmenupolicy legacy
 

paperfist

Diamond Member
Nov 30, 2000
6,539
286
126
www.the-teh.com
So in looking for the install KBB I did this:

wmic qfe get hotfixid

the results just return: KBB317935

There can't be just one hotfix installed...? Does that mean my Titanic just hit an iceberg?
 

paperfist

Diamond Member
Nov 30, 2000
6,539
286
126
www.the-teh.com
Well not sure if this is progress but I've managed to get a blue screen 0xc0000139 and even a safe mode screen however safe mode isxwhat takes me to the BSOD ahaha !
 

paperfist

Diamond Member
Nov 30, 2000
6,539
286
126
www.the-teh.com

RLGL

Platinum Member
Jan 8, 2013
2,113
319
126
Win 10 does not like dual boot for some reason. I was running dual boot earlier but had to do a fresh install and dump the other OS. There were all sort of things that somehow got cross linked between the two drives. Both were spinners.