none
Windows updates crashing Windows 7 machines with error code 0XC0000225 RRS feed

  • Question

  • We have had a handful of Windows 7 machines, upon reboot from installing updates crash, stating either No OS found or Boot Device Inaccessible. 

    You can pull the hard drive out and mount it on another system and see the Windows directory, access all the files and folders. 

    We tried booting from a bootable media and running the following commands from the command prompt:

    bootrec /scanos

    bootrec /fixmbr

    bootrec /fixboot

    bootrec /rebuildbcd

    All of these seem to be a success except te very last one, as it states the directory doesn't exist. In the end, we've had to reimage each of these machines. 

    I was able to pull event logs off a few of the machines and started looking through. There are no error messages related to failed Windows Updates.

    Only common thing I can find is they are all Dell 7470's. However, we have had a lot more of the 7470's update and reboot with no issue. So it's not the entire line of machines.  And we didn't have any issues like this during testing.

    Right now, we have remote associates shipping laptops back, and don't have spares to ship them in the mean time. Has anyone else come across this? Apparently on Reddit, a few have and ended up reinstalling Windows as well.

    Wednesday, September 25, 2019 1:30 PM

All replies

  • These are trial and error steps:

    Open Windows RE > Administrator:X:\windows\system32\cmd.exe > X:\Sources: >

    Type these commands.  (Comments will be in parenthesis)

    1) bcdedit /enum

    2) bcdedit | find "osdevice"

    (note the partition drive letter for later commands)

    3) dism /image:W:\ /cleanup-image /revertpendingactions

    (change the drive letter to the partition drive letter displayed in the prior result)

    4) dism /Image:W:\ /Get-Packages

    (change the drive letter to the partition drive letter displayed in the prior result)

    (Find the package(s) that were just installed by date.)

    (Run the following command on the last installed package:

    examples:

    5) (dism.exe /image:W:\ /remove-package /packagename:Package_for_KB4014329~31bf3856ad364e35~amd64~~10.0.1.0)

    dism /image:W:\ /remove-package /packagename:Package_for_KB982664~31bf3856ad364e35~amd64~~6.1.1.0 

    6) (Reboot)

    7) (The remove package command can be repeated to remove multiple recent updates as  needed)

    8) chkdsk /r /v W:  (change the drive letter W to the partition drive letter from the osdevice command)

    (This may take time to complete.  If the command is able to proceed it typically will display an estimated time as ETA.)

    9) sfc /scannow /offbootdir=W:\ /offwindir=W:\windows  (change the drive letter W to the partition drive letter seen in the find osdevice command.

    10) (There are additional troubleshooting commands)
    Wednesday, September 25, 2019 5:23 PM
  • Fails on the first step:

    1) bcdedit /enum

    The boot configuration data store could not be opened.

    The requested system device cannot be found.

    Yet i can pull the drive and access it via an external connection. And if i reimage them, it works fine. So what ever happened, seems to have hosed something a bit bigger than the BCD.

    Wednesday, September 25, 2019 6:25 PM
  • Check the results for steps 4 and 5 in this link:

    https://neosmart.net/wiki/0xc0000225/

    If the above fail then type:

    c:

    dir

    d:

    dir

    e:

    dir

    and determine the Windows drive letter in Windows RE.

    It should display: bbi, bcd-template, components, default, drivers, elam, sam, security, software, system, vsmidk, journal, regback, systemprofile txr, etc.

    All of the file sizes should be sizable. If it displays zeros then abort.

    Make a new directory and name it backup or something similar.

    17) type: MD backup

    Copy all of the files into this new directory.

    18) type or copy and paste: copy *.* backup

    It should now display: bbi, bcd-template, components, default, drivers, elam, sam, security, software, system, vsmidk indicating the files were copied.

    Change the directory to regback

    19) type: cd regback

    It should now display: c:\windows\system32\config\regback>

    20)type: dir

    It should display: default, sam, security, software, system etc
    All of these files must be sizable. If it displays zeros then abort.

    21) type or copy and paste: copy *.* ..

    It should now display: 
    DEFAULT
    Overwrite ..\default? (yes/no/all):

    22) type: a
    It should now display: sam, security, software, system and that the files were copied.

    23) type: exit

    24) click turn off your PC
    Remove the USB flash drive if you had changed your boot order. Otherwise you can leave it and power on your computer.

    Wednesday, September 25, 2019 7:33 PM
  • Hi, 

    Which update did you installed? What KB number? 

    This error code 0XC0000225 might caused by many reasons, such as Windows updates or certain programs. 

    Since you have re-imaged these machines, to find the root cause, we need to reproduce the issue.

    For the bootrec /rebuildbcd not working issue, please refer to this link

    https://social.technet.microsoft.com/Forums/en-US/0ca88e19-0929-4b23-a617-5bd7b84756ef/rebuild-bcd-bootrec-rebuildbcd-is-not-working-cboot-path-not-found?forum=win10itprogeneral

    Best regards. 


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, September 26, 2019 10:06 AM
  • Tried that. Errors out on the step to set the selected partition as active. States the MBR is on a fixed disk.

    Event tried setting the OS partition to active, same error message.

    Since i was booted of a bootable thumb drive, i could tell i had the right disk based on size. As the thumb drive listed as a 16GB drive.

    Thursday, September 26, 2019 3:43 PM
  • What was displayed during regback?
    Friday, September 27, 2019 7:28 AM
  • Sorry for the late reply. 

    It was displayed as soon as you attempted the fix. In the end, my boss said to no longer waste time trying to fix it, we just reimaged the drives.

    still want to know what happened as we have had 10 out of 1300 machines

    Wednesday, October 2, 2019 2:48 PM
  • Hi,

    It might caused by different reasons. 

    Since we do not have anything we can analyze, we can not find the exact reason. 

    If this problem happened again, please save the logs. 

    Best regards. 


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Friday, October 4, 2019 7:08 AM