Windows 10: Microsoft .Net Runtime UAC Pops Up Every Few Minutes

I have a user getting prompted by UAC every few minutes regarding Microsoft .Net Runtime requesting admin credentials. Every time the user clicks No, UAC comes back after a few minutes shown below:Nothing in our security stack is flagging as malicious or blocking anything from this user's device. However, I did find some logs that are related to the UAC prompt issue. Shown below is an output of one of the logs:[0B54:0AD4][2022-11-22T07:08:58]i001: Burn v3.14.0.5722, Windows v10.0 Build 19044: Service Pack 0, path: C:\Users\User~1\AppData\Local\Temp\{85268AAC-6881-41DB-85FA-9DF

:)

 

Microsoft Visual C++ Runtime Library

Did not work. Runtime Error window still pops up.

Any other suggestions are appreciated...

 

Microsoft .NET Framework, Unhandled exception

Hi,

Welcome to Microsoft Community.

I suggest you to un-check and recheck .Net framework 3.5 and .Net framework 4.6 advance series from Windows features.

Try the following steps:

• Press Windows + R keys to open Run command.
• Type Appwiz.cpl and select "turn Windows feature on or off" from the left
• Uncheck .Net framework 3.5 and .Net framework 4.6 advance series.
• Restart the computer
• Repeat step 1 and 2 and check .Net framework 3.5 and .Net framework 4.6 advance series.
• Restart the computer.

Regards,

 

Microsoft .Net Native Runtime Package 1.1.23101.0

This fix worked for me:

Perform the following steps:

• Open the Task manager. Here’s a tip: Press CTRL+Shift+ESC.
  
• Click File > Run New Task
• Make sure you have a check mark beside “Create this task with administrative privileges”
  
• Type Powershell
• Type the following in the Powershell prompt:
  
  $manifest = (Get-AppxPackage Microsoft.WindowsStore).InstallLocation + '\AppxManifest.xml' ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest
  
• Close the Powershell window
• Reboot

It was posted by a Microsoft support engineer who deserves a promotion! There were several threads on the support forums asking for help with this issue, and all of the other basic "fixes" proposed by the MS reps didn't work. Whoever Deepak Raghav is,
thank you!

Original thread link:

Redirecting