Warning of possibility the latest Microsoft KB4056894 update which I think its the one for the Intel/AMD exploit when installed on a Windows Server 2008R2 x64 (otherwise fully upto dated) with dual AMD Opteron CPUs caused a STOP error on reboot. This latest Microsoft fixed bluescreened one of my company servers and nothing I tried would get it to boot, safe mode=no, DSRM=no, last known good configuration=no, just got STOP 0x000000c4 each time within a second of main boot. In my case it was on a HP Proliant DL385 G2 with AMD Opteron CPUs thats a DC and Exchange server so it was important to get it up and running and ideally not lose todays emails. Our other proliant DL380's all with Intel Xeon's took the update and rebooted with no issues so think its restricted to AMD or specially Opteron CPU. Have spent a few hours trying various things without luck trying to fix it from recovery console command prompt and finally found a way to uninstall the update from this command line and once done it booted up fine. I've now rechecked Windows update, the KB4056894 is appearing again as an important update but this time its getting HIDDEN For reference, the command I needed was (note when in recovery mode my servers usual C: OS drive with Windows etc showed up as e: drive Code: dism /image:e:\ /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24002.1.4 /scratchdir:e:\temp To list installed updates you can use this command. Luckily the only item installed with todays date was at the bottom of the long list it generates Code: dism /image:e:\ /get-packages /format:table /scratchdir:e:\temp
Thanks Kermit. Reminds me of the painful troubleshooting when trying to restore from a recovery partition and remembering the drive being another letter can waste you a ton of head scratching time.
Looks like its not just me and someone else with a similar CPU but Win7 x64 [which is same ballpark as Server 2008R2 in terms of kernal] also had the problem with the update on a PC with Dual Opterons and found the same solution as me although I'm pleased with myself for working it out independently https://answers.microsoft.com/en-us...-2018-01/f09a8be3-5313-40bb-9cef-727fcdd4cd56 Mine's the Simon (UK) post as think MS need to withdraw that update for Opterons and work with AMD to get it right.
Thanks for this. We only have 1 Opteron (not Operton right ?) based server at work and haven't yet installed the update due to how critical it's needed, but I'll hold off on the update for now. Luckily, the system itself is pretty isolated so no major concerns for Spectre/Meltdown.
did you not get a statement from your MS/AV provider? lot of AV's need to be updated to edit registry keys & not cause major issues, over wise you will see BSOD after the updates. caused by the AV solutions Linux works ok of course..
i have that update,went on no prob on my Win 7 machine, but it was from yesterday, not sure if it's for this Meltdown exploit?
true, but AV's are also causing BSOD this is even on Intel CPU's so dont apply the update willynilly.
I have disabled Windows Update on my Windows 10 systems for now until I see what happens. Windows 7 is check for updates but I see one of these is available. I can’t be bothered with annoying issues with things not fully tested right now. I don’t need headaches if things go wrong with these patches.
here you go constantly being updated: https://docs.google.com/spreadsheet...iuirADzf3cL42FQ/htmlview?usp=sharing&sle=true
https://www.theverge.com/2018/1/9/1...t=chorus&utm_medium=social&utm_source=twitter Looking here, it seems to be K8 based CPUs that are suffering the issue. Quick seach on OP's server model seems to point the Opteron in his server is K8 based. Need to check mine, can't remember if it's K8 or K10 based.
Some are worse than others, talk about fact checking, i don't know where they got this information from but had they even read more than two lines of whatever the source was it would have looked pretty much the same as all the rest of them do, IE making it clear its only 10 year old Athlon CPU's that are affected. Tom Warren really is the most useless journalists on the net, everyone but him at least got the facts right.
