KB4058258 Inaccessible boot device on Intel CPU

This does not work, uninstalling the KB after the servicing stack executed doesn't recover the deleted device driver files. 

I did a system restore, to a point where the KB was installed but before the servicing stack run. Uninstalled the KB, but the same service stack remained, and after it was executed (with KB removed) I lost again all my devices and got unbootable system. So it looks like I need to restore to an earlier point, before this KB was installed initially.

Is there any way to make this thread public? I can see it only when logged in, but not when just browsing without logging.

My last restore point already has it, it is easy to spot by just looking at the list of affected programs.

I did however disable the Scheduled Task \Microsoft\Windows\Servicing\StartComponentCleanup, left my computer overnight and the servicing stack didn't run, still have my acpi and disk.inf files.

I guess I'll wait until after another update something else will be shown in registry under Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version and then let it run.

I've been seeing a bit of what I'm guessing is this problem: the system spontaneously starts throwing an INACCESSIBLE_BOOT_DEVICE blue screen on startup because of a missing acpi.sys. I haven't tried looking for an underlying cause on my own, but I do have a fix to get things to boot:

(No guarantees. This may make things even worse. The following steps are for people who know what they're doing.)

(Windows 10 installation media is freely available from Microsoft.)

1. Get to a Windows 10 recovery environment: Boot from a Windows disc or recovery partition; either works.

2. Bring up a command prompt. (Choose an option -> Troubleshoot -> Advanced options -> Command Prompt)

3. Restore acpi.sys to (probably C, D, or E):\Windows\System32\drivers either from a working machine, Windows disc, or the recovery environment itself. The last one is easiest if it works.

Make sure acpi.sys has a matching CPU architecture (i.e. 32-bit vs. 64-bit), or your system won't boot. For Windows 10.0.16299.15, 32-bit acpi.sys is 496 KB, 64-bit acpi.sys is 716 KB. These figures will change somewhat for earlier or later builds of Windows 10.

It's probably a good idea to make sure acpi.sys comes from a computer running the same build of Windows 10. I haven't tried otherwise. "dism /Image:(probably C, D, or E):\ /?" will give you an "Image Version" (look for that specific text) of the broken Windows installation if you don't know that off-hand. Build numbers are four numbers separated by periods, i.e. "10.0.16299.15"; the first three numbers are generally what matters (i.e. "10.0.16299").

The recovery environment has its own copy of acpi.sys in X:\Windows\System32\drivers.

4. Load the SYSTEM hive from the broken Windows installation: At the command prompt, run "regedit", select Computer\HKEY_LOCAL_MACHINE, go to File -> Load Hive, and select (probably C, D, or E):\Windows\System32\config\SYSTEM. You will be asked for a key name; type "fuzzy-lumpkins", and select OK.

5. Go to HKLM\fuzzy-lumpkins\ControlSet001\Services\ACPI, and:

5a. Delete the "DeleteFlags" value.

5b. Change the "Start" value to 0.

6. Go to HKLM\fuzzy-lumpkins\ControlSet001\Enum\ACPI_HAL\PNP0C08\0, and:

6a. Delete the "InstallFlags" value.

6b. Change the "ConfigFlags" value from 0x00000020 (32) to 0.

7. Go to HKLM\fuzzy-lumpkins\ControlSet001\Enum, and search (Ctrl+F) for InstallFlags anywhere under HKLM\fuzzy-lumpkins\ControlSet001\Enum. If you find any, delete "InstallFlags" and change "ConfigFlags" to 0, like in steps 6a/6b.

This is likely to find your hard drive (something like SCSI\Disk&Ven_VBOX&Prod_HARDDISK\4&2345abcd&0&000000, which varies depending on the model of your drive), as well as the Microsoft Virtual Drive Enumerator (ROOT\vdrvroot\0000).

8. Optional: Search HKLM\fuzzy-lumpkins\ControlSet001\Services for anything containing DeleteFlags. Repeat steps 5a and 5b for each disabled service, and copy in matching drivers like step 3.

9. Exit the command prompt, then "Continue -- Exit and continue to Windows 10" (i.e. reboot). Ideally, the system will boot normally.

10. If the system instead boots back into the recovery environment, go back to the command prompt, and do "bcdedit /set {default} recoveryenabled no". Then reboot again.

...And that's it. Note that there's nothing in here to prevent Windows from doing this to you again. And nothing in here restores missing .inf files, etc./so on/so forth.

Good luck to anybody who tries this. And remember: this is your fault for trying to use a computer.

FIXED FIXED FIXED FIXED FIXED FIXED FIXED FIXED FIXED FIXED

Method 1:
Crash the computer a few times on purpose (This will trigger a Windows 10 Automatic Repair)
Get to the Windows Automatic Repair screen
Advanced options
Run a System Restore
Restore to a time before the crash
Reboot
You may only get one shot at this
Start
cmd (Right Click Command Prompt and Run As Administrator)
Command Prompt
dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.214.1.17
Press Enter (Return)

This is the same fix for INACCESSIBLE BOOT DEVICE from another older package name Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9 and substitute this package name for the one listed in the Method 1 above.

In January, computers received INACCESSIBLE BOOT DEVICE from the January roll up called 16299.192.1.9  

In February, other computers received INACCESSIBLE BOOT DEVICE from the February roll up called 16299.214.1.17 

If you already ran a DISM to remove the package during an Windows Automatic System Repair, there have been instances that the package is no longer valid to remove and you are hosed plenty. Attempt to repeat the multiple crashes, run another system restore and then attempt an in-place upgrade or boot to a fresh Windows Media Toolkit for Windows 10 and be sure to choose the option to KEEP MY FILES AND APPS and not the KEEP MY FILES. The difference is KEEP MY FILES AND APPS is the option that keeps all of your programs installed without having to reinstall everything! The package will install itself quickly after reboot and force pending operations that make the next boot a complete start over. If you have to start over, because of the BIOS you are using and the Spectre/Meltdown update provided from Microsoft, disable this update by using the Microsoft Catalog Update to stop it, or get into Windows 10 Settings and change the optional updates to 365 days(that's the max), the security updates to 30 days (that's the max) and Pause the updates (1 month max). There is not platform that is immune to this bug. We have seen it on DELL, HP, LENOVO, Toshiba, Surface. We have also seen the USB ports not working out there too. There has been mention of SSD and firmware for some SSD drives causing this too. Also, a simple corrupted bcdedit/bootrec cure for this error as well. Easy rule: If it happened after a Windows Update, it was likely a Windows Update. If it happened after a hard lockup and the computer was forced off, the hard disk should be the focus for a chkdsk.

None of this is recommended by Microsoft for Security purposes
All of it is recommended by MILE Technologies (us) for functionality and business continuity.

-miletx.com