If Start Menu, Settings, Search, Cortana, Microsoft Edge, Action Center and other Windows components are not responding in Windows 10, please try these fixes.
Method 1:
• Run PowerShell as admin.
• Run this commands
Get-AppXPackage -AllUsers |Where-Object {$_.InstallLocation -like “SystemApps“} | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}
Situation: The client is using Office 365 with MFA. One of users can’t verify MFA when login Outlook. When she tries, Office 365 call her phone and she followed the instruction press #, but it doesn’t verify it.
Troubleshooting: Restart the Outlook and try it again. It works!
Situation: The client has XP computer running Xray software. After cleaning data and restarting it, they gets Blue screen with stop: 0000007B, F78A2524, 00000034, 00000000.
Troubleshooting: 1. choose Last known good configuration doesn’t fix the problem.
2. Safe mode doesn’t work.
3. Unplugging external devices such as external hard drive, printer, NIC, eternal USB, it boot as normal. Plugging all external devices except hard drive. It works. The hard drive causes the problem.
Situation: When installing Windows 10 update, you may receive this message: Error code: 0x80073712 and Some update files are missing or have problems.
Troubleshooting: 1. Run System File Checker. Run command line as admin. Then this command: sfc /scannow.
2. Restart Windows Update Service or restart Windows.
3. Download Windows Update Troubleshooter to troubleshoot it.
4. Run Deployment Image Servicing Tool (DISM). DISM is a built-in Windows tool that can be used to repair and prepare Windows images, including the Windows Recovery Environment, Windows Setup, and Windows PE. It is usually able to fix various problems related to the Windows operating system. To run a DISM scan, open Command Prompt as administrator and type this command: “DISM /Online /Cleanup-Image /RestoreHealth”. Press Enter on the keyboard to execute it
5. Remove Pending Xml File
If you are unable to update the Windows operating system, you might want to remove the pending .xml file and try to start the Windows Update process again. Open Command Prompt as administrator and type the following commands (remember to press the Enter key after you type each command):
net stop trustedinstaller
cd %windir%\winsxs
takeown /f pending.xml /a
cacls pending.xml /e /g everyone:f
del pending.xml
6. Reset Windows Update Components
Faulty or damaged Windows Update components can also cause Windows Update error code 0x80073712. To fix the problem, reset them manually using Command Prompt and its commands. Open Command Prompt as administrator and type the following commands (press Enter after each):
net stop bits
net stop wuauserv
net stop appidsvc
net stop cryptsvc
ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak
ren %systemroot%\system32\catroot2 catroot2.bak
net start bits
net start wuauserv
net start appidsvc
net start cryptsvc
Restart the computer
7. Rename Software Distribution Folder
Software Distribution folder is a temporary folder in which Windows stores the update files until they are completely downloaded. Then, Windows starts the updating process. Renaming this folder might solve the problem and fix the Windows Update error code 0x80073712. To rename this folder, use Command Prompt. Open Command Prompt as administrator and type the following commands (press Enter after each):
net stop wuauserv
ren c:\windows\SoftwareDistribution softwaredistribution.old
net start wuauserv
Exit Command Prompt and restart the computer.
8. Download Windows update manually and install it. Please refer to this post:
Download and install Windows 10 update manually
9. Download and install Windows Update Assistant from Microsoft. This step by step video may help:
Situation: The client has a Windows 2012 R2 server and shared some folders. However, no one can access it with System error 53.
Troubleshooting: If we disable the Windows firewall, we can access the server. After test, we find the client has blocked TCP port 445 and DFS Management (SMB-In). we fix it by disabling these rules.
Situation: the user receives this message: Your system administrator does not allow the use of saved credentials when using RDP to access a remote server.
Troubleshooting:
on the client, go to Control Panel -> Credential Manager. You will see three sections:
1.Windows Credentials
2.Certificate-Based Credentials
3.Generic Credentials
Remove the credentials from Windows Credentials and add it to Generic Credentials.
Situation: the client is running RD Services on Windows 2012 and the licensing seems to be configured correct. RD Licensing Diagnoser or Get-RDLicenseConfiguration don’t show any errors.
However, EventID: 1128 shows TerminalServices-RemoteConnectionManager error.
Troubleshooting: Even they have 5 users login the RD Server, but the RD licensing manager shows all licenses are available and no licensees are used.
The solution was to delete the REG_BINARY in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod
Situation: the client is running RD Services on Windows 2012 and the licensing seems to be configured correct. RD Licensing Diagnoser or Get-RDLicenseConfiguration don’t show any errors.
However, EventID: 1130 shows TerminalServices-RemoteConnectionManager error.
Troubleshooting: Even they have 5 users login the RD Server, but the RD licensing manager shows all licenses are available and no licensees are used.
The solution was to delete the REG_BINARY in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod
Situation: the client is running RD Services on Windows 2012 and the licensing seems to be configured correct. RD Licensing Diagnoser or Get-RDLicenseConfiguration don’t show any errors.
However, remote users receive this message when accessing the RD server: “The remote session was disconnected because there are no remote Desktop License Servers available to provide a licence”.
Troubleshooting: Even they have 5 users login the RD Server, but the RD licensing manager shows all licenses are available and no licensees are used.
No remote Desktop Licence Server availible on RD Session Host server 2012 – 360ICT – Technical Blog
The solution was to delete the REG_BINARY in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod
Situation: The client is running Relius Administration and just upgraded it to version 2019. One of users has a problem to login with this message: This version of Relius Administration is not currently licensed.
Troubleshooting: The version needs to be upgraded or the user didn’t do it right.