March patches relax antivirus restrictions.
If you’ve not been offered any security updates since January there’s a reason. It appears that some Antivirus programs make unsupported API calls to Windows kernel memory that interfere with January’s updates (especially Meltdown and Spectre patches) and may lead to BSoDs (Blue Screen of Death). To protect customers Microsoft have stopped offering security updates to devices with unsupported AVs.
While waiting for a fix from AV vendors (and if you’re absolutely sure you know what you’re doing) you can
temporarily disable the compatibility check. The fix is just a registry key:
Path : HKLM \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ QualityCompat Type : REG_DWORD Value : cadca5fe - 87d3 - 4b96 - b7fb - a231484277cc Data : 0x00000000
According to Microsoft as of March 13-th most of the AV vendors have fixed their products so the compatibility check will be removed soon.
You can find more information here:
You have a Windows 10 1703 computer / VM and you have upgraded it to version 1703. When you run sysprep it fails with the following error:
Posted in Windows, Операционни с-ми, Технологии |
Tagged 1703, 1709, Error, Generalize, MiraCast, Sysprep, Windows 10, Windows 10 1703, Windows 10 1709, Windows.MiracastView_22.214.171.124 |
While upgrading to Windows 10 1709 Enterprise via WSUS your clients may report the following error:
(Unable to find resource):ReportingEvent.Client.167; Parameters: Feature update to Windows 10 (business editions), version 1709, en-us
This may happen to other versions too
Posted in Windows, Операционни с-ми |
Tagged Error, esd, IIS, KB3095113, Mime, Mime type, mime type esd, Tips, Tricks, Upgrading, Upgrading to Windows 10, Upgrading to Windows 10 through WSUS, Windows 10, Windows 10 1607, Windows 10 1709, WSUS |
It may happen to receiveDsRemoveDsServerW error 0x5(Access is denied.) in NTDSutil. Here’s my short recipe:
1. Ensure your account has domain admin rights
2. Ensure CMD/NTDSUtil was started with elevated rights (RunAs Administrator)
3. Open Active Directory Sites & Services:
Navigate to the site/server you want to cleanup Right click on the “NTDS Settings” object > Properties > Object
Ensure “Protect object from accidential deletion”
Saves hours of debugging 🙂