Cumulative Update KB4487044 Windows 10 v1809 Build 17763.316 - Feb. 12 Win Update

Hi,

Installed this CU on 4 machines now. Pretty fast too.

Disk Cleanup has never been faster on my machines, 10 minutes at most. Strange how things can vary....

Cheers,

slicendice said:

Yeah, I'll leave it over night.

I now know why it's so slow. It freaking decompress every update file there is and then deletes the unconpressed files one by one and finally deletes the comoressed one.

How horrible is that? It would take me 1s to delete the contents of SoftwareDistribution/Downloads folder and everything would be running smoothly still.

I don't know the process involved when running disk cleanup to remove the amount of GB Windows Updates-related, but you seem to have a good idea about it. OTOH, I don't think it will take all night, but I know for a fact that it could be pretty long, especially with 6.9GB, just enough to put one at wit's end.

Bree said:

After updating to 17763.316 I can now access my router's web admin page using Edge again.

Did you do it without using the workaround mentioned in this thread's first page. If so, why are they (MS) saying it is still a known issue:

Known issues in this update

Symptom

Workaround

After installing KB4480116, some users report that they cannot load a webpage in Microsoft Edge using a local IP address. Browsing fails or the webpage may become unresponsive.

Open the Control Panel and select Internet Options. On the Security tab, select the Trusted Sites icon. Select the Sites button. Clear the check box for Require server verification (https:) for all sites in this zone. In the Add this website to the zone: box, type the local IP address that failed to load, such as http://192.168.0.1. Select the Add button. Select the Require server verification (https:) for all sites in this zone check box. Select the Close button. Select the OK button. Restart Microsoft Edge. Microsoft is working on a resolution and will provide an update in an upcoming release.

@Bree,

I have just tried it (local IP address) in Edge without the workaround, and it worked. My guess is, as far as I remember, I had to use the same workaround before this update and it is probably still working.

IronZorg89 said:

Did you do it without using the workaround mentioned in this thread's first page. If so, why are they (MS) saying it is still a known issue:

They say it's a known issue after installing KB4480116 - and that is correct, that's when my issue started...

Known issues in this update

Symptom
After installing KB4480116, some users report that they cannot load a webpage in Microsoft Edge using a local IP address. Browsing fails or the webpage may become unresponsive.

...but this is KB4487044 and it fixed the issue. No workarounds were used on any of my machines.

The known issues of this CU has been updated, the Edge bug no longer appears.

Bree said:

They say it's a known issue after installing KB4480116 - and that is correct, that's when my issue started...


...but this is KB4487044 and it fixed the issue. No workarounds were used on any of my machines.

Meaning it shouldn't be tagged as a known issue for this CU (KB4487044) because it has been fixed. It was then (KB4480116), but not anymore. Just my way of seeing things!

IronZorg89 said:

Meaning it shouldn't be tagged as a known issue for this CU (KB4487044) because it has been fixed. It was then (KB4480116), but not anymore. Just my way of seeing things!

It was a 'cut and paste' error and shouldn't have been there, now been updated to say....

Known issues in this update

---

Microsoft is not currently aware of any issues with this update.

@Brink will no doubt update post #1 shortly....