locked
INACCESSIBLE_BOOT_DEVICE after latest Windows Update RRS feed

  • Question

  • Anyone else getting INACCESSIBLE_BOOT_DEVICE on multiple computers after recent updates? Plenty of machines now in 2 days where rebooting after patching has broken Windows 10. System restore does not work, safe mode does not work. Read around on forums and tried everything. Ended up reinstalling Windows :-(
    Friday, May 12, 2017 10:42 AM

Answers

  • In our case these patches were in pending state, removal of the packages fixed the problem. I assume F-Secure Software Updater has something to do with it.

    Package Identity : Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~14393.1198.1.6

    State : Install Pending

    Release Type : Security Update

    Install Time :

     

    Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.1066.1.8

    State : Install Pending

    Release Type : Security Update

    Install Time : 12-05-2017 13:45

     

    Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.1198.1.6

    State : Install Pending

    Release Type : Security Update

    Install Time : 12-05-2017 13:42


    Here is a link to the fix:

    https://community.ivanti.com/thread/35248

    Solution can also be found here:

    https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/windows-10-get-inaccessiblebootdevice-after-update/9da8a71e-891a-4e80-8b8a-bcbc2f4f945c


    • Edited by Knorre Tuesday, May 16, 2017 10:09 AM edit
    • Proposed as answer by Kate LiMicrosoft employee Tuesday, May 16, 2017 10:23 AM
    • Marked as answer by Knorre Tuesday, May 16, 2017 10:24 AM
    Tuesday, May 16, 2017 10:05 AM

All replies

  • We are experiencing the same problem.

    Several machines are unable to boot after the major Windows update this week.

    We have about 10 to 20 customers with this error and haven't found a fix that works on everyone.

    Some of them have been repaired and some have been reinstalled.

    Friday, May 12, 2017 12:42 PM
  • Hi Palmer!

    I'm having the same issue with few (for now) win10 machines! You mentioned "Some of them repaired.."  All the machines  I' ve seen having this issue I've had to restore from "old" automatic Win7 backup images. They didn´t restore to any found restore points.

    Do you mean getting back to previous restore point??  or repaired some other way??  

    Friday, May 12, 2017 7:51 PM
  • Do you mean getting back to previous restore point??  or repaired some other way??  

    I wonder if this is another symptom of Boot File Servicing?

    C.f.
    https://answers.microsoft.com/en-us/windows/forum/windows_10-update/kb4015217-failed-to-install-on-xps-13/7959b40b-cf67-4cb7-b9f3-d1f7e382b1e7?page=2&tab=question&status=AllReplies 



    Robert Aldwinckle
    ---

    Saturday, May 13, 2017 5:43 PM
  • getting more and more computers with same problem. Lenovo and Dell manufactured. No fix in sight :-(
    Monday, May 15, 2017 6:22 AM
  • Same here. around 5% of our pc's affected so far. started may 11. All running windows 10 + bitlocker. Using restorepoints worked on a few pc's, but mostly didn't work and had to do a reinstall keeping user files.
    Monday, May 15, 2017 7:42 AM
  • Hi, 

    Would you please let us know what the certain update you got? 

    I just would like to configure if this issue is happened after you get MS17-010 for Windows 10 security update. 


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

    Monday, May 15, 2017 8:17 AM
  • Winver:

    1607 OS Build 14393.0

    Monday, May 15, 2017 10:01 AM
  • same her with a dell latitude E6530

    Monday, May 15, 2017 10:06 AM
  • Currently for us we have problems with:

    lenovo m 7052-a9g

    lenovo m 2992-d9g

    Dell Optiplex 3020

    Dell Optiplex 390

    Monday, May 15, 2017 10:17 AM
  • I managed to gather logentries from windows.old from one of the affected pc's.

    I dont think it is related to ms17-010, as

    KB4013429 was installed on the pc back in march 17. (if i read the logfile correctly).


    two updates was installed before the reboot and crash:

    - EventData
    UpdateTitle Sikkerhedsopdatering til Windows (KB4019472)
    CommandLine "C:\WINDOWS\system32\wusa.exe" "C:\ProgramData\F-Secure\FSOFTUPD\deploy\Windows10.0-RS1-KB4019472-x64_delta_DA.msu" /quiet /norestart 

    - EventData
    UpdateTitle "Sikkerhedsopdatering til Windows (KB4020821)"
    CommandLine

    "C:\WINDOWS\system32\wusa.exe" "C:\ProgramData\F-Secure\FSOFTUPD\deploy\windows10.0-kb4020821-x64-RS1_DA.msu" /quiet /norestart 

    I don't know it it is important that it was f-secure that initiated and pushed the update...

    Monday, May 15, 2017 3:15 PM
  • Same Issue on various PCs (with/without EFI).

    I also have the kb4019472 and the kb4020821 (and some office updates) as last updates before the problem and f-secure, but I haven't used f-secure to start the updates (the PCs was left powered on)

    I've tried to debug the boot error (with windbp on a remote pc) to see if there is same other information, and it seam a driver problem.
    Here's the information I have found:

    https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/windows-10-get-inaccessiblebootdevice-after-update/9da8a71e-891a-4e80-8b8a-bcbc2f4f945c

    Would be awesome to find a way to repair that/reinstall only the kernel, without reinstall all the application...

    Thanks


    • Edited by dmant-osdb Tuesday, May 16, 2017 9:20 AM forgotten some information
    Tuesday, May 16, 2017 9:18 AM
  • In our case these patches were in pending state, removal of the packages fixed the problem. I assume F-Secure Software Updater has something to do with it.

    Package Identity : Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~14393.1198.1.6

    State : Install Pending

    Release Type : Security Update

    Install Time :

     

    Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.1066.1.8

    State : Install Pending

    Release Type : Security Update

    Install Time : 12-05-2017 13:45

     

    Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.1198.1.6

    State : Install Pending

    Release Type : Security Update

    Install Time : 12-05-2017 13:42


    Tuesday, May 16, 2017 9:46 AM
  • In our case these patches were in pending state, removal of the packages fixed the problem. I assume F-Secure Software Updater has something to do with it.

    Package Identity : Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~14393.1198.1.6

    State : Install Pending

    Release Type : Security Update

    Install Time :

     

    Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.1066.1.8

    State : Install Pending

    Release Type : Security Update

    Install Time : 12-05-2017 13:45

     

    Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.1198.1.6

    State : Install Pending

    Release Type : Security Update

    Install Time : 12-05-2017 13:42


    Here is a link to the fix:

    https://community.ivanti.com/thread/35248

    Solution can also be found here:

    https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/windows-10-get-inaccessiblebootdevice-after-update/9da8a71e-891a-4e80-8b8a-bcbc2f4f945c


    • Edited by Knorre Tuesday, May 16, 2017 10:09 AM edit
    • Proposed as answer by Kate LiMicrosoft employee Tuesday, May 16, 2017 10:23 AM
    • Marked as answer by Knorre Tuesday, May 16, 2017 10:24 AM
    Tuesday, May 16, 2017 10:05 AM
  • Thanks for your sharing on this case, please mark your post as answer so that other communities who encounter the similar issue as yours can find the solution more efficiently.

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

    Tuesday, May 16, 2017 10:22 AM
  • Thanks Knorre! 

    So you also deployed the updates using f-secure?

    Tuesday, May 16, 2017 12:34 PM
  • if it's lenovo just switch off Lenovo Service Engine in bios
    Monday, September 30, 2019 11:07 PM