Use the System File Checker tool to repair missing or corrupted system ...
To resolve this problem, perform the System File Checker scan in safe mode, and make sure that the PendingDeletes and PendingRenames folders exist under %WinDir% \WinSxS\Temp. Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log %WinDir% \Logs\CBS\CBS.log.
Recover lost files on Windows 10 - Microsoft Support
Use this app to try to recover lost files that have been deleted from your local storage device (including internal drives, external drives, and USB devices) and can’t be restored from the Recycle Bin.
MS10-081: Vulnerability in the Windows common control library could ...
Resolves a vulnerability in Windows Explorer that could allow remote code execution if a user visited a specially crafted webpage.
Clear the Delivery Optimization cache - Microsoft Support
Delivery Optimization in Windows 10 clears its cache automatically. Files are removed from the cache after a short time period or when their contents take up too much disk space. However, If you need more disk space on your PC, you can clear the cache manually.
KB4134601 - FIX: "Could not load file or assembly 'Microsoft ...
Fixes a problem in which you receive a “Could not load file or assembly 'Microsoft.AnalysisServices.AdomdClientUI” error message when a Process Full operation is run in SQL Server.
November 21, 2017—KB4055038 - Microsoft Support
How to get this update. This update will be downloaded and installed automatically from Windows Update. To get the standalone package for this update, go to the Microsoft Update Catalog website.
You can't access OWA or ECP after you install Exchange Server 2016 CU6
After you install and upgrade to Microsoft Exchange Server 2016 Cumulative Update 6 (CU6), you can't access Outlook Web App (OWA) or Exchange Control Panel (ECP), and you receive the following error message: We can't get that information right now. Please try again later.
Exchange Server setup fails with error code 1619 if it's started from ...
Error code is 1619. Workaround. If you use PowerShell, the setup must be started as .\setup.exe. Status. Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. References. Learn about the terminology that Microsoft uses to describe software updates.
MS10-081 : Une vulnérabilité dans la bibliothèque de contrôles commune ...
Résout une vulnérabilité de l'Explorateur Windows qui pourrait permettre l'exécution de code à distance si un utilisateur a consulté une page Web spécialement formée.