New
#80
Last time I was in a Windows specific forum I was running 7. But I registered to say this: This is the wackiest error I have ever seen in Windows, and I've been around since 2.0! (Yeah, I'm seeing my 50th birthday in my rear view mirror...) Yesterday I did an update search, and I installed a security update and KB4490481 on my two months old Surface Pro 6 i7, connected to a Surface Dock with two monitors, keyboard and a few dongles. Restarted normally, and then came to the log-in screen. And after the PIN, it went straight from the log-in picture to bluescreen.
I tried without the docking in case it was something there, same thing. Then I did what is the wacky thing here: I logged into my backup account (literally backup, an administrator privileges account I use it to back up all documents and stuff from my main account to my server). WITHOUT PROBLEMS! This being a new computer I had not done a full backup of the documents, only incremental (which I do from my main account). So I had never logged into the backup account before, and it got set up as a normal Windows 10 account when I logged into it, without any problems. And then I could do the full backup, before I started tinkering. I installed a few new Surface specific updates (firmware and drivers), hoping that would help. Restarted, went to the main account...BOOM! New crash. I used my bar code app on the phone, but it only took me to a general support page, with the "have you tried to restart your computer" bullshit. So the 3D bar code on the blue screen didn't say antyhing specific. But I could still log in to the newly set up account. So I used that to uninstall the update. And this is written from my regular account. Go figure!
According to Blue Screen View the culprits are ntoskrnl.exe, three times alone and one each with win32kfull.sys and hal.dll as coconspirators. Does this tell anybody anything?
Last edited by Mastiff; 06 Apr 2019 at 05:04.
"already up to date", But you don't have it (KB4490481) in Update history. Like I mentioned before, you can try the direct download link to get it from the Microsoft Update catalog —See the first page of this thread— but make sure to have a restore point first or preferably a system image backup. This will definitely let you know if you can get this update to install to completion or not.
As I said in post #73 above....
My guess is it has been withdrawn from windows update, possibly because of too many reports like this....Cumulative Update KB4490481 Windows 10 v1809 Build 17763.404 - April 2 Windows Update - Page 5 - Windows 10 Forumslike doctorwizz above also have BSOD on every machine I have after restarting to complete this update.
I can confirm that on every un-updated machine I have (VM or otherwise) windows update will not find it. I'd take that as a hint it would be better not to install it manually. After all, it has no new security fixes and Patch Tuesday is justfive days way.
It's just three days now until the regular monthly update, which will include fixes from this one (and more), so I'd wait if I were you.
I don't want to be argumentative, but I have just tried the direct download link to the Microsoft Update Catalog in the first page of this thread and it is still working. Don't you think that if it were removed, the link wouldn't be working anymore. Maybe there are other issues besides the removal that are responsible for this update not to work on some machines.
Confirmed. It seems to have been reinstated. All my machines that couldn't find it when I tested this on 4th April now find and install KB4490481.