• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Creator updates keep hosing my Win10 install

paperfist

paperfist

Diamond Member
The last Creators update (fall I believe) and now the most recent one have left me out of commission with boot config blue screen stop errors.

I run my install from a m.2 drive. Are these errors common or related to my drive?

Current error is 0xc00000d
 
I haven't had any of those type of issues on my PCs from Windows Update. Maybe download CrystalDiskInfo and see if your drive is reporting any errors.
 
UsandThem said:
I haven't had any of those type of issues on my PCs from Windows Update. Maybe download CrystalDiskInfo and see if your drive is reporting any errors.
Click to expand...

Thanks I'll try that after I get back up and running,

I haven't run into boot issues since Win '95 lol
 
XavierMace said:
I've had zero issues with any of the updates on any of my Win 10 systems. Can you give us the full text on the stop error?
Click to expand...

Your PC/Device needs to be repaired

The boot configuration date file is missing some required information.

File: \Boot\BCD
Error code: 0xc000000d

You'll need to use recovery tools.
 
memtest86 7.4 is my current preference assuming your system is UEFI capable. Having said this, when I first read your responses I thought you were referring to two different update scenarios but apparently just one. It wouldn't hurt to do a memory test though.

I'd start with checking the SMART stats as someone else suggested. If you can connect the disk to another machine you can read off the event logs on that machine and see whether it has been complaining about anything in particular lately. Running chkdsk /f /v /r on the M2 drive's file systems seems like a good plan.

If you can't boot Windows at present (I don't know if you know how to make this problem go away albeit temporarily), I'd boot from Win10 setup media and tell it to do startup repairs and the chkdsks from there.
 
mikeymikec said:
memtest86 7.4 is my current preference assuming your system is UEFI capable. Having said this, when I first read your responses I thought you were referring to two different update scenarios but apparently just one. It wouldn't hurt to do a memory test though.

I'd start with checking the SMART stats as someone else suggested. If you can connect the disk to another machine you can read off the event logs on that machine and see whether it has been complaining about anything in particular lately. Running chkdsk /f /v /r on the M2 drive's file systems seems like a good plan.

If you can't boot Windows at present (I don't know if you know how to make this problem go away albeit temporarily), I'd boot from Win10 setup media and tell it to do startup repairs and the chkdsks from there.
Click to expand...

The system doesn't boot. I do have UEFI.

I don't have another system capable of running the m.2 drive.

I guess what I'll attempt to do first is see if I can clone the failed Win 10 system and then use another drive to install Win10 on so I can troubleshoot the dead one.

The last time I tried to rebuild the boot block/configuration files I spent a large amount of time and ultimately it didn't work and I had to do a fresh install.

Is there any alternate ways to install Win10 so that I don't have to rebuild all the apps, data files, games, settings, etc when it does fail or is everything still tied to the registry?
 
I've had 50/50 luck with bootrec, I wouldn't rule it out. I once wasted a lot of time by not verifying whether the OS expectation for UEFI and the BIOS settings were in alignment though because bootrec doesn't tell you if you're wasting your time because the settings don't match up.

Everything is tied to the registry.

Has the system being playing up at all leading up to this?
 
mikeymikec said:
I've had 50/50 luck with bootrec, I wouldn't rule it out. I once wasted a lot of time by not verifying whether the OS expectation for UEFI and the BIOS settings were in alignment though because bootrec doesn't tell you if you're wasting your time because the settings don't match up.

Everything is tied to the registry.

Has the system being playing up at all leading up to this?
Click to expand...

Nope zero issues and that's what's frustrating and confusing. In both cases I delayed the update installs until finally they trigger on their own. It's the same system with no changes where I've run into this non booting issue after and update.
 
Had a case like this, brand new 1709 install about a month ago and the past three weeks it would bluescreen on boot and was fixed with bootrec but we needed a permanent solution. The last time I went out to remedy it, I used the dism /revertpendingactions command instead and it took care of it (see 'questionsformicrosoftproducts' post here for more). Survived this week so we'll see how it goes..
 
paperfist said:
Nope zero issues and that's what's frustrating and confusing. In both cases I delayed the update installs until finally they trigger on their own. It's the same system with no changes where I've run into this non booting issue after and update.
Click to expand...

If you do manage to resurrect the install, then you can use MS's tool for hiding specific Windows updates. I had problems with this before (ie. it didn't immediately work) but I wonder if combined with plio's suggestion that it might be enough to stop the pending update install and my suggestion then stops the update from being installed in future.
 
Exactly what version number do you have and what version number are you trying to install? There are some versions that will not update to the Creators update 16299. 0000. Is your current OS on the same m2 drive?
 
PliotronX said:
Had a case like this, brand new 1709 install about a month ago and the past three weeks it would bluescreen on boot and was fixed with bootrec but we needed a permanent solution. The last time I went out to remedy it, I used the dism /revertpendingactions command instead and it took care of it (see 'questionsformicrosoftproducts' post here for more). Survived this week so we'll see how it goes..
Click to expand...

Oh yeah I remember learning all those dism commands the last time. There was one that told me what updates were installed, and then I used dism to remove it. It didn't work I think because I had already played around with boot rec and automatic repair. In hind site I think if I did that first I could have saved the install.
 
RLGL said:
Exactly what version number do you have and what version number are you trying to install? There are some versions that will not update to the Creators update 16299. 0000. Is your current OS on the same m2 drive?
Click to expand...

Honestly I don't know which version. I believe it's set to auto update, but for the last month it's been asking to do one of those large updates and I delayed it.

1709 I believe is the last one that killed my OS and I had to do a fresh install. This update is after that.

Yes, OS in on the m.2 drive along with everything else.
 
What's your hardware configuration? Just so we can help determine if it's an incompatibility issue possibly.
 
Well memtest is showing no errors. I didn't fully understand the crystal disk test but everything was green.

More troubling is I booted up a copy of Win10 from a USB stick and viewing my m.2 drive shows it is empty. That doesn't make sense though as I wouldn't get a BSOD when I try to boot.
 
The can mean that the Drive is really empty but there is hidden boot parttion section that dose not show on Win Explorer.


😎
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top