Cumulative Update KB4025342 Windows 10 v1703 Build 15063.483

WU does not pick up KB4025342 on my primary laptop.

I then tried installing KB4025342 cumulative update from catalog and I got 'The update is not applicable to your computer': https://support.microsoft.com/en-za...cable-to-your-computer-error-when-you-install

Huh? Well, it explains why WU is not picking it up.So I thought I'd try KB4022716. But it's been pulled from MS catalog.

WU troubleshooter repeatedly shows this i.e. on successive runs.

Issues found

Service registration is missing or corrupt Fixed
Reset service registration Not run

Potential Windows Update Database error detectedPotential Windows Update Database error detected
Possible issues may prevent Windows Update from keeping your system up to date. Fixed
Repair Windows Update Database Corruption Completed

Windows Update components must be repaired
One or more Windows Update components are configured incorrectly. Fixed
Repair Windows Update components Not run

Check for pending updatesCheck for pending updates Fixed
Download and Install pending updates Completed

Well, at least I'm not the only one: Cumulaitve Update KB4025342 causing errors in Update Troubleshooter
except he could at least install the KB.

sfc /scannow shows no integrity violations.

Also, other Windows Updates e.g. WD, Office are working fine.

So I thought I'd try the KB4025342 delta update! It all went like clockwork, until the the last moment: KB4025342 was not installed.

This is on my newest laptop, three older laptops all updated fine.

So I either give up, and hope a future update sorts this out, or I (reluctantly) try resetting WU? Reset Windows Update in Windows 10

Edit: Retried delta update, and now also got the 'not applicable' message there ...

Windows Defender is still not fixed. The Advanced Settings in the Firewall and Network Protection area is still not working. Sent multiple feedbacks to Microsoft and no luck.

Windows runs great overall, just sucks to see things that are broken in Windows

lmaneke said:

Windows Defender is still not fixed. The Advanced Settings in the Firewall and Network Protection area is still not working. Sent multiple feedbacks to Microsoft and no luck.


Windows runs great overall, just sucks to see things that are broken in Windows

Hello mate,
I had this problem too, with settings in the firewall and network. This cumulative update KB4025342 has fixed the problem. I can't see any other problems.
See you
Czecher

lmaneke said:

Windows Defender is still not fixed. The Advanced Settings in the Firewall and Network Protection area is still not working. Sent multiple feedbacks to Microsoft and no luck.

Windows runs great overall, just sucks to see things that are broken in Windows

You can get to the advanced settings through the control panel, though I agree the control panel shouldn't be hidden if the Windows 10 settings equivalent is broke.

You can also get there via the Windows 10 settings -> Network & Internet -> Windows Firewall

lmaneke said:

Windows Defender is still not fixed. The Advanced Settings in the Firewall and Network Protection area is still not working. Sent multiple feedbacks to Microsoft and no luck.

Windows runs great overall, just sucks to see things that are broken in Windows

Maybe you should try to reset Windows Firewall with the following command line in a command prompt with admin privilege:

netsh advfirewall reset

Sometimes, that's all it takes to get things back to normal.

IronZorg89 said:

Maybe you should try to reset Windows Firewall with the following command line in a command prompt ...
Sometimes, that's all it takes to get things back to normal.

It's not Windows Firewall that's broken, it's the Windows Defender Security Center. On the 'Firewall & network protection' page there are five blue links near the bottom. The one that should take you to 'Advanced settings' doesn't work. It does (since this update?) produce a UAC prompt, but even if you click 'Yes' nothing happens.

You can get to Advanced settings through Control Panel > All Control Panel Items > Windows Firewall, so it's available, just not from the Windows Defender Security Center.

Bree said:

It's not Windows Firewall that's broken, it's the Windows Defender Security Center. On the 'Firewall & network protection' page there are five blue links near the bottom. The one that should take you to 'Advanced settings' doesn't work. It does (since this update?) produce a UAC prompt, but even if you click 'Yes' nothing happens.

You can get to Advanced settings through Control Panel > All Control Panel Items > Windows Firewall, so it's available, just not from the Windows Defender Security Center.

How about uninstalling the update (roll back), for this is probably the only way to see if the issue has to do with the recent CU as you have mentioned. After the uninstall, if the problem doesn't reiterate itself, then, we can start from a firm ground into resolving the issue by pausing automatic update in order for it (CU) not to reinstall. That would be a good start until a fix is found..

On the other hand, if the problem still persists, one can start digging a little bit deeper by running dism.exe (restorehealth) or even try a repair upgrade.

IronZorg89 said:

How about uninstalling the update (roll back), for this is probably the only way to see if the issue has to do with the recent CU as you have mentioned....

No, I was saying this problem has always been there and that the recent CU still hasn't fixed it. Here it was reported back in April...

Anyone else have this problem in the new Windows Defender that when going to Firewall & Network protection tab in the left column and then clicking on "Advanced settings" in the links on that tab, a prompt appears to give permission to load the settings but when clicking Yes, nothing comes up after that?

Creators Update - Discussion of new changes and quirks

On the other hand, if the problem still persists, one can start digging a little bit deeper by running dism.exe (restorehealth) or even try a repair upgrade.

Actually, until May 19th DISM was broken in 1703 too... :)
Creators update component store shows corruption but unable to repair