Windows 10: New Build Won't Install

I'm currently running 11082 and Windows update is attempting to push 14257 out to me but it's failing to install. The update downloads ok, but when I restart I boot into the windows repair menu instead of the upgrade screen. I've tried to do an automatic repair, but when attempting that I get the message "the drive windows is installed on is locked"

The only thing I can do is reboot, at which point I boot right back into 11082 with no problems.

I have no idea why the update isn't installing and I don't even know where to go look for an error message or something like that.... any help?

:)

 

New Win 10 build 15031

That definitely woudn't affect your games when you play it on the new build,,

The new build will just enhance some features on the Insider program//Windows 10 and it won't affect the apps or games installed..

 

Windows 10 USB 3.0 error 0xc0000225 won't work!

Since it's a new build it will definitely be UEFI so the media has to be booted as UEFI flash stick or it won't install.

 

Hi cls and welcome to Tenforums.

First, turn off Fast Startup

To understand what this is/does (it was first introduced in Windows 8):
“Fast Startup (aka: hybrid boot or hybrid Shutdown) is a new feature in Windows 8 to help your PC start up faster after shutting down. When turned on, Windows 8 does this by using a hybrid shutdown (a partial hibernate) method that saves only the kernel session and device drivers (system information) to the hibernate (hiberfil.sys) file on disk instead of closing it when you shut down your PC. This also makes the hiberfil.sys file to be much smaller than what hibernate would use (often 4GB or more). When you start your PC again, Windows 8 uses that saved system information to resume your system instead of having to do a cold boot to fully restart it. Using this technique with boot gives a significant advantage for boot times, since reading the hiberfile in and reinitializing drivers is much faster on most systems (30-70% faster on most systems tested). If you have a motherboard with UEFI, then fast startup will be even faster.”

Problem is, when you shutdown your system and then restart it, if your "hibernated info" is corrupted, W10 will try to load it, and can fail with an error that the drive is locked.

Then, grab the esd file from your 14257 download:
Show hidden files
C:\$Windows.~BT\Sources\install.esd

Use the tutorial here to convert to an ISO, then mount the ISO and run it from within your current 11082. Make sure all other drives and external devices are disconnected when doing the upgrade.

*Please make sure you have imaged your drive before doing this, in case you need to go back.*

Hope that helps!

 

Well, that didn't exactly "work" but I am getting somewhere. I disabled fast startup, created the ISO and attempted an update. It still failed in exactly the same way, after it first restarted it booted me into a the recovery startup menu.

However, after rebooting out of that, my 11082 build did boot right up and the Windows 10 Setup wizard was on my screen with an actual error message.

OxC1900101 - 0x20017
The installation failed in the SAFE_OS phase with an error during boot operation.

So I'm not exactly sure that that means... but now that I at least have some more info I'm hoping someone can advise further. Setup error log is attached.

 

Failure right after the first boot is a driver issue. I'll have a look at your log.
In the meantime, please run sfc /scannow and CHKDSK on your OS drive.

 

I had already ran chkdsk successfully and had started an SFC /SCANNOW run, which looks like it's "stuck" at about 58%. I may not be giving it enough time, but it was steadily moving along until it hit this snag and has been stuck for maybe 30 minutes now? Not sure what to do here... but that's probably not a great sign?

One of the google links i hit regarding my error suggested that removing bluetooth drivers might help, and I *did* add a bluetooth adapter to my machine recently. But I uninstalled those drivers and tried the update again, it still failed. Perhaps I needed to unplug the adapter as well..

 

Let it go. It may take some time. Reboot and run it again. I'd like to see you run it at least 3 times, (rebooting after each run), or until you get the message "no integrity violations found".

I am seeing "vclone.sys" errors, "asmbsw.dll" errors, "IphlpsvcMigPlugin.dll" errors and printer errors.

I need you to fill in your system specs. I specifically would like to know your Processor.

Do you have a Macrium image of your OS and all data backed up before we do this?


Once the sfc is completed 3x, if there are still "errors that cannot be repaired", please type in the box Code: findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"[/quote] and post the text file it saves on your desktop.


****************once I have seen the sfcdetails.log******************
VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV
Since you're having this trouble, I will go back to some recommendations from early-on upgrades:
- remove all peripherals (printers, USB flash devices, external HDDs, BT, etc., everything except keyboard, mouse and monitor)
- uninstall any 3rd party AV, HDD monitoring software, MSNMessenger/Windows Live components (seems to be corrupt/missing?)
- uninstall your printer, all drivers and software
- if you've moved your libraries, move them back for now
- open device manager and go through each one, right-clicking and auto-checking for updates.
- run disk cleanup, deleting old OS files (Windows.old) - if you need instructions please let me know.


Run the upgrade "disconnected" from the internet; chose update drivers later if the option appears.

EDIT: Yes, I am seeing a network error as well - that could be the BT.

 

I can't seem to figure out how fill out my system specs in profile but:

Processor: Intel i7 3770k
Motherboard: Asus Maximus V Gene-Z
Video Card: Asus Nvidia Geforce GTX670
RAM: 16gb

• SFC completed and I've since run it twice more, both of these last two runs returned "did not find any integrity violations" I've attached the CBS logs with today's entries.
• I don't have any AV or HD monitoring software installed.
• I ran through the disk cleanup process about a week ago, will do so again
• Attempted to update all of my device drivers as requested.
• My printer is network (if that matters) but I will uninstall that device
• I will uninstall the bluetooth adapter again (and physically remove it)
• I will remove all usb devices

Then I'll try the upgrade again and report back with results.

 

Okay thanks.
Here's how to do it:
System Specs - Fill in at Ten Forums - Windows 10 Forums

Okay, since we've now got a clean bill of health from SFC, and everything is physically removed, yes go ahead and disconnect from the internet and try running setup.exe from within the OS and upgrade that way.

 

After taking all th steps mentioned above and also disabling my network adapter, the upgrade failed again in exactly the same manner. Upon restart it tries to boot into the "Setup" process and almost immediately fails to the recovery menu.

Same error from the setup wizard when I got back into my 11082 build of windows. *Sad I've uploaded my latest setuperr.log but that isn't telling *me* much. (I do see it still complain about a printer even though I removed it from device manager)

This is getting frustrating... anything else we can think of to investigate or try?

 

Yeah, I'm seeing the same errors as before.
Well, I'm running out of ideas. I suppose, you could make a Macrium image of your HDD, then try a clean install using your newly created ISO from the ESD file? If it won't clean install, you can at least restore the 11082 from the image. FWIW, I've seen some people complaining about serious problems with this new build on some systems...maybe your system needs to stay away from it for a while? *Wink

 

Thanks for all the help.

Seems like maybe I should just sit this release out and try again when the next build is released. If it still fails then I'll have to think about a fresh install.

 

Sounds like a plan! Sorry we couldn't get it installed, but maybe it's for the best.

 

To close the loop on this... I did end up figuring out my issue.

I tried to to a clean install, but after booting off the USB drive the Windows Setup program was unable to see the SSD I use as a system drive, although it could see the larger hybrid drive I use for data.... weird.

So I rebooted and checked BIOS and sure enough, the SSD wasn't showing up in the SATA configuration... which is real odd because it was listed as a boot option and the computer would boot into the Windows install on that drive with no problem... so it must've been seeing it at some point?

Anyways, I just re-seated the SATA cable which got the drive showing up in BIOS. After doing that, the windows 10 upgrade succeeded without any issue.

I can't imagine this is a typical problem, but again, just wanted to close the loop.