DISCLAIMER: You're going to be messing with your system files in this. Your PC is already screwed. If you mess this up it's possible to make the problem worse. I am not responsible or liable for anything that happens as a result of you incorrectly implementing the steps in this document.
THE PROBLEM
Some of you may be aware that Microsoft's latest builds of Windows 10 are bricking some older machines by making their boot device disconnect mid-boot. I want to note that while MS says this is limited to AMD devices - my machine that suffered this was an i7 3770 on a z68 gigabyte UD3 motherboard running the latest bios. The absolute worst part about all of this is they come down as mandatory updates without warning. This is difficult to fix - but it can be done if you have access to the Advanced boot options and can get the command prompt.
So, lets start with the offending KB's: KB4054517 and KB4056892. If you have a computer running x58 or z68 and your windows is still working... DEFINITELY DO NOT INSTALL THESE. This also applies to ALL AMD SYSTEMS to my knowledge. You'll note that MS states this is resolved by KB4056892, but that is not my experience. Installing either of these will make your PC unable to boot.
THE FIX
The first thing you need to do is determine if you're on build 16299.125 or 16299.192. If you are on 16299.125 you will have to do an extra step of first installing 16299.192. If you are on 16299.125, you will also need a USB stick that can hold 650MB for the 16299.192 CAB file.
- Boot into Advanced recovery mode using either your recovery partition or some installation media. You should be able to let your computer restart until it offers you Automatic Repair with "Restart" and "Advanced Options" then click on "Advanced Options."
- Choose "Advanced Options," "Troubleshoot" then "Command Prompt."
- Identify your system disk, mine loaded up as E:, but you may end up on a different drive letter - which will affect the majority of the commands, change anywhere you see e: below. You can do this by switching to the various disks, and using dir to look at the filesystem until you find your system disk.
- Switch to your system disk and create a temporary folder: mkdir temp
- Run DISM /image:e: /scratchdir:e:\temp /get-packages
- Verify you have a 16299.125 or 16299.192 build in the list. It will likely be one of the most recent updates.
IF you are on 16299.192.x.x
1. Disable any possibility of network access to the computer. Unplug the ethernet cable, or unplug the wifi card. This is so windows doesn't just go and re-upgrade the machine.
2. Use your mouse to highlight the Package Identity value, in my case: Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.125.1.6
3. Run dism /image:e: /scratchdir:e:\temp /remove-package:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.125.1.6
5. Use your mouse to highlight the Package Identity value, in my case: Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9
6. Run dism /image:e: /scratchdir:e:\temp /remove-package:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9
7. This should complete successfully and a reboot will get you going.
8. Continue onto disabling windows update section below.
IF you are on 16299.125.1.6
1. Fortunately, you can supersede this update with the other broken update 16299.192.1.9 noted above.
2. Unfortunately, this means you need a second computer to solve the problem, running an unaffected windows install.
3. Using your second, working computer, Download KB4056892 update from microsoft to get the .MSU file.
4. Create a temp folder on the C: drive of your working computer.
5. Unpack the .MSU file to get the .CAB file so you can manually install 16299.192.1.9 using DISM with the command expand -F:* windows10.0-kb4056892-x64_a41a378cf9ae609152b505c40e691ca1228e28ea.msu c:\temp
6. Copy the expanded KB temp file to your usb stick. It should be named Windows10.0-KB4056892-x64.cab
7. Plug the USB stick into the computer that won't boot, and identify the drive letter assigned to the USB stick as previously done to identify the system drive. In this case, mine was I:
8. Use DISM to install the package: DISM /image:e: /scratchdir:e:\temp /add-package /packagepath:i:\Windows10.0-KB4056892-x64.cab
9. If this completes. Exit the command prompt and restart your PC. Let it crash a couple times then follow the instructions for 16299.192.1.9 above.
Disabling Windows Update
This is where things get really bad. Windows Update will automatically reinstall one of these two updates, leaving your PC unbootable again. This is why we airgapped the computer earlier by disabling network access entirely. If you're on Windows 10 Pro, you can disable Windows Update until this gets sorted out. If not - you'll need to explore other options.
1. Create a system restore point immediately before doing anything else. System restore will allow you to recover from this problem an infinite amount of times by resetting your PC to this state. You'll lose program updates, and some other things, but saved documents, etc, should be safe.
2. Click start and type gpedit.msc to load the group policy editor.
3. Expand Computer Configuration -> Administrative Templates -> Windows Components -> Windows Update
4. Change "Do not display 'Install Updates and Shut Down' option in Shut Down Windows dialog box" to Enabled
5. Change "Do not adjust default option to 'Install Updates and Shut Down' in Shut Down Windows dialog box to Enabled
6. Change "Configure Automatic Updates" to Disabled
This should prevent Windows Update from bricking your machine again. Hunker down and wait for the dust to settle. Eventually they should get this sorted out and have an update that will fix your machine while not leaving it unbootable.
Submitted January 23, 2018 at 08:50AM by zoson http://ift.tt/2DzIq1B
0 komentar:
Post a Comment