QualityCompat flag

B

Bournesup

Member
Lately, the rollup updates for January and February of 2018 require this registry flag to be set

Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat" Value="cadca5fe-87d3-4b96-b7fb-a231484277cc" Type="REG_DWORD”
Data="0x00000000”

I've tried integrating the registry key into the setup, or via reg file. Neither approach works. The value is not set.

This flag is necessary for the correct installation of these rollups

kb4056894
kb4074598

ntlite version being used 1.3.0.5025
 
Windows 10 cumulative update KB4074592 comes with just a single known issue, and it’s actually a bug that’s been there since a few months ago.

Microsoft says that antivirus solutions running on systems deploying this update must have a dedicated registry key set – this is a requirement for all security products, and unless compatible, computers might be blocked from receiving further cumulative updates.

Code: 
Contact your antivirus manufacturer to verify that their software is compatible and that they have set the following REGKEY on the computer:
Key="HKEY_LOCAL_MACHINE
"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat"
Value Name="cadca5fe-87d3-4b96-b7fb-a231484277cc"
Type="REG_DWORD”
Data="0x00000000”

KB4074592 installed correctly on our testing systems running the Windows 10 Creators Update, and judging from the feedback posted online, the process has been completed smoothly for the majority of users as well.
Click to expand...
Source:
http://news.softpedia.com/news/windows-10-cumulative-update-kb4074592-issues-519797.shtml

Eset software workaround fix:
https://support.eset.com/alert6668/

kb4074590 info:
https://support.microsoft.com/en-us/help/4074590/windows-10-update-kb4074590
 
The question is with regards to using ntlite. The integration of the above two rollups being successful is when the registry key is present. This is during the integration process of installing the updates.
 
That key as stated is just for an antivirus tools to set.

I have tested now and the integration works correctly. It might be that WIM install resets it during the process, in that case add the REG to the post-setup page.
You can confirm the value in the WIM by opening the Hives on the Registry page.

Also please update the tool, or send me a PM what is the reason to keep that one.

Thanks.
 

Attachments

  • test.reg
    352 bytes
Last edited:
My last tool update which I have, and haven't tried was 1.4.1.5590. When I bought the tool, it allowed for one year of updates.

Is there a difference in how the reg file is applied. There is only a slight difference.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat]
"cadca5fe-87d3-4b96-b7fb-a231484277cc"=dword:00000000

I believe my reg is in hex and yours is in decimal for the value, and the key is surrounded in square brackets.
 
I misunderstood the update policy too. You can still update to the latest and it will still work. The only thing that wouldn't work are any new features that were added since your license expired. For example, I am using 1.5.0.6025 on last year's license (even tho I renewed and got a new ID) and it works fine.
 
Secondly, the version after that showed that kb4038803 that sp1 needed to be installed as a prerequisite. Which I thought as strange since I am using sp1 already integrated into the ISO. And the ISO came from microsoft.
 
Bournesup said:
Secondly, the version after that showed that kb4038803 that sp1 needed to be installed as a prerequisite. Which I thought as strange since I am using sp1 already integrated into the ISO. And the ISO came from microsoft.
Click to expand...
Ignore that warning, only applies to 7 without SP1.

There are 2 newer updates:
the latest is KB4041681
 
I tried 1.5.0.6025 success the registry value was set correctly, however, the desktop icons, and folder options were not. I included a copy of my preset. The current preset does not have the same tweak section as the previous preset.


Correction, my apologies, tweaks are now under the section labelled setting.

Also, the integration and customization using my previous preset took significantly longer. Almost 30 minutes longer. Strange, my cpu is not on the list of cpu's affected by intel's hardware bug.
 

Attachments

  • Auto-saved session {65CAF905-5E50-4A42-900B-5E14084871E9}.xml
    54.9 KB
  • previousPreset.xml
    56.5 KB
Last edited:
@Bournesup, in the new preset there are no Settings set. It's not your fault per say, the preset saving scheme was changed in the meantime due to some found limitations with the old one.
In other words, you will have to reselect your old settings in the UI and save a new preset. At least there is a quick fix :)
 
You must log in or register to reply here.
Back
Top