Cumulative Update KB4507453 Windows 10 v1903 build 18362.239 - July 9 Win Update

These known issues remind me of the warnings on the side of medication bottles..... We can make you feel better but your nose might fall off.

Brink said:

UPDATE 7/26:

New item added to "Known issues".

Unfortunately I have never got Reset_Reregister_Windows_Update_Components.bat to successfully complete. I always get too many file access errors or not found errors.

Hi,

This past Sunday the 15th and Monday the 16th I've had a controlled folder access pick on CLSID {6CED0DAA-4CDE-49C9-BA3A-AE163DC3D7AF} this is a

Code:

Defender Shield Broker
Security Health Agent Activate As Activator Host
Windows Security
\REGISTRY\MACHINE\SOFTWARE\Classes\CLSID\{6CED0DAA-4CDE-49C9-BA3A-AE163DC3D7AF}

And thinking that something may be wrong with updates I went to run the SFC >Dism-Restorehealth >SFC sequence but it wouldn't run in an elevated powershell, it did complete successfully in an elevated CMD prompt.

I couldn't get past the SFC scan as powershell threw a Windows Resource Protection could not start the repair service error. This was seen before and after I completed the SFC >Dism-Restorehealth >SFC sequence in an elevated CMD prompt.

I am up to v1903 | Build - 18362.356 and as mentioned here I to didn't get a MSRT. My Defender updates have been successfully installed over the 15th, 16th, and 17th so I'm not sure if the CLSID SNAFU is related to the MSRT.

The questions I have are;

• Is running the SFC >Dism-Restorehealth >SFC sequence in a CMD prompt the same as running it in powershell?
• And does anyone think there may be something amiss with my Powershell prompt and if so, how do I repair it?

For now all I can do is watch if I get any more controlled folder access picks on that CLSID.

Thanks Wynona, now that you mention it I do seem to recall PS not working sometimes.

Guess what I found, the update part at the bottom is the important part:

pokeefe0001 said:

Module Installer was not the problem so I tried the Tweaking.com tool. Repair services 26 &27 didn't help.

It looked like one of the preliminary tests in the tool was an execution of SFC and it ran fine. I thought maybe it was because I was in Safe Mode, but that was not the case. SFC/Scannow still refuses to start even in Safe Mode.

DISM next, or is it even an option if SFC won't start? (Sorry if that is a dumb question.)

Update: Some serious user stupidity here. I've been trying to run SFC from a desktop icon (using Run as administrator). It fails to start that way. However, it runs ifI use the Command Prompt (Admin) from the right-click Start menu. So I obviously have something wrong with my desktop icon. I just recreated icon from the Apps list and it works now. I guess I'll mark this "Solved".

I just tried running PS like the OP did, from the Start menu list instead of the icon on my taskbar an by golly it worked! Guess I'll have to create a new taskbar icon. though somewhere along the line the icon must of got borked 'cuse it worked before.