- #Problem signature 05 autofailover windows 7 update
- #Problem signature 05 autofailover windows 7 windows
#Problem signature 05 autofailover windows 7 windows
I also had him uninstall Avast as that updated when the Windows updates installed, so I figured that could have got corrupted as well.
#Problem signature 05 autofailover windows 7 update
Maybe the "Failed to config Windows updates, reverting" routine reinstalled that update again. I thought I'd try uninstalling the updates it did the first time he booted it but although it did 7 then, it now only lists 2 from that date (26/09), KB2859537 which is the one we already installed the other day so I don't know why that's back and KB2836943.
It said that the first time we booted in this mode earlier today as well, before I tried uninstalling that update, but without forcing a reboot. After that, it still shows that each time but then continues to the desktop. Reverting" and the first time after uninstalling that update, it said it had to reboot and did so automatically. Booted into Safe Mode (without networking) again, went into Device Manager and disabled the onboard Qualcomm Atheros NIC (as it boots in Safe Mode but not in Safe Mode with Networking it seemed worth trying) but that still BSOD as well.Įvery time it boots into Safe Mode (without networking), it says "Failed to configure Windows Updates. Did a clean boot as per but that still resulted in the BSOD.Ĥ. Booted into Safe Mode (without networking) again and uninstalled KB2859537 as this article suggests it can cause BSOD on boot I'm not sure this was one of the updates that was applied today before it started BSOD, as that article's dated 13 August so I think I'd probably already installed that and it hadn't caused any problems but it seemed worth a shot. Anyway, I didn't want to interrupt it if it was doing something, so we let it run but although it said it had identified some problems and was fixing them, after about 10mins it said it had failed and showedĢ. Selected Startup Repair instead of Boot Normally (by accident, my brother was too slow to change it, before then it had defaulted to Boot Normally every time anyway, so it took him by surprise). I looked in the Win7 圆4 Windows\Minidump folder whilst booted to the VHD and there wasn't any files dated today, only one from August and another from some other non-recent date, so there's no help there.ġ.
I've got a EaseUS ToDo Backup System Image that he could revert to (I added the Boot disk to the grub4dos menu) but that's the nuclear option as I think I made a few changes since making that and it will be tricky to talk him through using that as I won't be able to connect to his machine to do it for him, so I'd rather try and fix the problem if at all possible. It had installed about 7 Windows Updates some time before the power got cut but we hadn't had a chance to reboot, so they may have not been installed fully and maybe that's why it reverted them, I'm not sure.
When he booted into this mode, it said it was reverting some updates. He managed to boot it with Safe Mode (without networking) but obviously that doesn't allow me to connect via TeamViewer to sort anything out. However, it did at least produce the Safe Mode, Last Known Good Config, etc options but Safe Mode with Networking and Last Known Good both still just result in the BSOD. On the "Windows failed to shutdown properly" screen it only shows Boot Normally and Repair Windows, no Safe mode or Last Known Good Config.īooting to the VHD, I used BootICE to add another entry to the Windows boot menu, Win7(Safe), set in BootICE to use Safe mode, but selecting this just gave him a BSOD as well.