KB 4487017 Feb Cumulative update for Win10 v1803 causing BSODs

Topic

New Reply

@weedacres reports that the Feb 2019 Cumulative Update KB KB4487017 for Win10 v1803  is causing BSODs. One of my customers called yesterday reporting
[See the full post at: KB 4487017 Feb Cumulative update for Win10 v1803 causing BSODs]

2 users thanked author for this post.

GreatAndPowerfulTech, woody

Reply | Quote

Replies

No problems to report here from any of our 1803 users. Dell Optiplex pc’s and Latitude laptops.

Red Ruffnsore

Reply | Quote

No problems to report on my v.1803 on Lenovo Legion.

Reply | Quote

Just to be safe I will skip that update…  I suggest anyone with 1803 to do the same.

Just someone who don't want Windows to mess with its computer.

Reply | Quote

I have all February updates approved and installed on literally hundreds of machines and none of them are blue screening.  These are almost entirely Dell Optiplexes, but there’s a few oddballs.

Reply | Quote

I installed the KB4487017 update here on Windows 10 Pro 1803 on 3/11.

No BSOD here.

Running a custom desktop PC with Intel Ivy Bridge 3rd generation Core CPU on Asus H61M series motherboard.

To track the cause down, I think I would start with collecting data regarding hardware configurations that are experiencing the error.

Windows 10 Pro 22H2

Reply | Quote

So why are BSODs from the February updates being reported so late? This makes us question if quality updates should ever be installed anymore. From what I know, there’s no way to install Group B updates on Windows 10.

I am no longer an active member of the forums.

Reply | Quote

Well, there’s just no way to do individual comprehensive testing in a short enough timeframe for these… especially for system stability.

I mean, that’s wildly variable, what with some problems only occurring after about a week of uptime, and…

Also wouldn’t mind 17134.590 being sort of bad if we had another known-good version with security updates, but .619 is unofficially considered a preview and .648 is still too new… let alone yesterday’s .677 which is like .619?

Reply | Quote

Interesting read from Microsoft ;

“Reminder: March 12th and April 9th will be the last two Delta updates for Windows 10, version 1803. Security and quality updates will continue to be available via the express and full cumulative update packages. ”

https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-quality-updates-explained-amp-the-end-of-delta/ba-p/214426

1 user thanked author for this post.

Great Lake Bunyip

Reply | Quote

Which seems to be saying the big pipes into corporate IT depts will be able to get smaller express updates but Joe Blow consumer with DSL will have to swallow the whole shebang.

 

Just because you don't know where you are going doesn't mean any road will get you there.

Reply | Quote

I installed KB 4487017 on 2/21/19 and have seen no real problems with it other than my networked computers no longer showing up under networks in File Explorer. They were all showing up until that update?

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

Absolutely! Version 1803 has been giving me random “Stop: Memory Management” BSOD’s. Hardware diagnostics and stress testing revealed NO hardware issues. Even running SFC and DISM has not fixed the issue. I have not tried removing the update yet. My brother in CA is also on 1803 ans experiencing the same problem. Windows cannot be operated as a software service because of the open platform of the PC and because there are too many variables in the real world to be able to test thoroughly. When are they going to get a clue? Oh yeah, they’re Microsoft…

Reply | Quote

Can you give us some information on the hardware and it’s specs that you are using? Perhaps we can narrow the problem down to specific hardware.

Ane let us know if uninstalling the update fixes the problem.

Reply | Quote

I’ve been getting those on various HP laptops with Intel iX-4* CPUs with every version of Windows 10 since 1607 except 1809, with varying frequency. On 1709 they were decently rare.

Nothing ever shows up on HP’s own diagnostics or others…

On 1809 get random crashes about as often but it doesn’t display that error – or any error at all. Might be the graphics drivers dying before the error gets displayed for all I know.

I’m not getting any useful kind of logging from these for some reason, but that isn’t new either.

Reply | Quote

Big question… are you SURE it’s related to the Win10 version?

Sounds like it could be a simple (!) intermittent hardware problem…

Reply | Quote

Sounds like an issue with HP systems. HP seems to throw a lot of their own software on their systems. I’m guessing one of their software packages is causing the issue.

Red Ruffnsore

Reply | Quote

The 001A BSODs indicate a memory management error.

This BSOD means that a severe memory management error occurred. BSOD error code 0x0000001A may also show “MEMORY_MANAGEMENT” on the same blue screen.

https://www.lifewire.com/blue-screen-error-codes-4065576

https://www.thewindowsclub.com/memory-management-error-0x0000001a

 

Windows 10 Pro 22H2

1 user thanked author for this post.

woody

Reply | Quote

An update on my original report of problems after kb4487017 was installed:

Both the affected PC’s are HP Pavilion 24-b227c AIO’s. They were purchased as Win 10 Home and I upgraded them to Pro when I installed them. All of the Win 10 PC’s that I maintain are Pro and all have updates deferred 24 days so the Feb Cumulative installed on 3/8.

One of the PC’s experienced 2 01A BSOD’s on 3/11 and had no repeat. The other started getting daily 01a’s when my customer logged on.

Since removing the update on 3/18 there have been no more 01A’s. I also take care of 15 other Win 10 Pro machines (mostly Dell) and none of them have reported the problem.

I’m hoping that this issue is somehow resolved with the March update…

Reply | Quote