SFC /verifyonly - Integrity violations (W11 24H2)

I

innovateusa

Member
Messages
47
Reaction score
3
When I use the gamer profile I get integrity violations on Win11 24H2. I a suspect it a package removed or multiple ones are triggering this, does anyone know which ones?
 
Go to NTLite folder and look for xml file in folder Presets - latest one which can be autonamed like Auto-SavedXXXXXXX.
Be sure delete any personal info ie. in UnAttended.
 
We talked over email, will continue here.

Ran SFC /Scannow without using NTLite prior, it fixes these for 26100.2605:
DEPLOY [Pnp] Repaired file: C:\WINDOWS\System32\drivers\BthA2dp.sys
DEPLOY [Pnp] Repaired file: C:\WINDOWS\System32\drivers\BthHfEnum.sys

and just this one for 26100.1742:
DEPLOY [Pnp] Repaired file: C:\WINDOWS\System32\drivers\bthmodem.sys

Meaning those we can ignore as they are a Windows bug.

Then edited with Gaming profile.
Key fact is if you enable any compatibilities - I kept them at default.

SFC found errors for a few components that is intentional (Copilot for example as some parts were needed to be kept while Microsoft detaches it better), and a few that is not due to shared files and owning component removed the NTFS links.
Will clean as much as possible by keeping those links and reply here when done.

Nothing concerning was found, all files were accounted for in WinSxS and SFC would report repaired with non-edited Windows as well.

Thanks.
 
Last edited:
I did get a clean sfc before I removed the additional components so I thought it was caused by one or more of the new component removals. I'm not quite clear on the compatibilities settings, what section should I check to revert that?
 
innovateusa said:
I did get a clean sfc before I removed the additional components so I thought it was caused by one or more of the new component removals. I'm not quite clear on the compatibilities settings, what section should I check to revert that?
Click to expand...
As stated over the email, I cannot replicate any SFC issue with Lite or Gaming template in the latest version.
If you do, just send me the preset and I'll do the testing.

Compatibility affecting this is SFC + Servicing Stack - it's enabled by default.

Make sure to read the log as described, and ignore the Bluetooth driver ones, explained above.
 
Sorry, I thought my profile was attached to the email, I'll attach here. Your gaming SFC is clean now, but I removed a few more packages I didn't want. I suspect one of them is causing the sfc issue.
 

Attachments

innovateusa said:
Sorry, I thought my profile was attached to the email, I'll attach here. Your gaming SFC is clean now, but I removed a few more packages I didn't want. I suspect one of them is causing the sfc issue.
Click to expand...
I did reply to your email with that preset;
that bluetooth driver is normal, please rescan full Windows before reporting.
 
Ok, sorry I must have gotten mixed up. If it's caused by the bluetooth driver I'll just put it back and try again, do you know where that is in the preset?
 
There is nothing to put back, it's not the removals.
Test Windows without NTLite, use a virtual machine and scan it, same result, I did it multiple times.
 
I guess I'm a bit confused - you don't think any of the additional packages I removed caused the issue? Since it passes without removing them, wouldn't that have to cause it? I'm using a physical machine to test with, I would think the results would be the same on a virtual one.
 
Let me know when you finish the test, use Windows 11 24H2, patch it, then scan and look inside cbs.log.
Mine had the Bluetooth issue described in the post above. Without NTLite that is.
Same I saw in your cbs.log that you sent me over the email.

Don't know what else to say to convince you except to reinstall to a VM or real, all the same.
 
Sorry, which test? Maybe I'm still missing something.
1. Fresh install of updated Microsoft 24H2 ISO: no integrity violations
2. Install of 24H2 ISO with gamer profile: no integrity violations
3. Install of 24H2 ISO with gamer profile (removed additional components and edited configure> settings) : integrity violations

Since the only change from 2 to 3 was the those component removals and setting changes, wouldn't that indicate that was the cause? I was thinking I could disable half, make a new iso and test, disable half again and test, ect. until I find which change caused it - gonna take quite some time for that though.
 
innovateusa said:
Sorry, which test? Maybe I'm still missing something.
1. Fresh install of updated Microsoft 24H2 ISO: no integrity violations
Click to expand...
I cannot confirm that, I had the Bluetooth in SFC same as yours, explained in the post above.

innovateusa said:
2. Install of 24H2 ISO with gamer profile: no integrity violations
Click to expand...
Unexpected.

innovateusa said:
3. Install of 24H2 ISO with gamer profile (removed additional components and edited configure> settings) : integrity violations
Click to expand...
The CBS.log you sent me in the email from that report had only bthmodem.sys, which is normal.
Open it yourself, sent you in the email how to read the log.

innovateusa said:
Since the only change from 2 to 3 was the those component removals and setting changes, wouldn't that indicate that was the cause? I was thinking I could disable half, make a new iso and test, disable half again and test, ect. until I find which change caused it - gonna take quite some time for that though.
Click to expand...
Which SFC error are we talking about?
Extract it from the log next time.

Thanks.
 
I believe it was an integrity violation, can I extract it from the log I emailed or should I make reload the ISO on a new pc?
 
innovateusa said:
I believe it was an integrity violation, can I extract it from the log I emailed or should I make reload the ISO on a new pc?
Click to expand...
Since I already reviewed your log, no need to repeat that.

Please deploy a fresh 26100.1742 ISO without removals and generate a fresh CBS log for confirmation that I'm not seeing things.
 
The one I downloaded from Microsoft has a SFC, but not after it's updated. Ntlite seems to update it when it installs so by the time I get into windows it will pass the sfc without error. I'm currently writing the stock MS one to a new USB drive, should have it installed in next hour and can send that CBS log.
 
You must log in or register to reply here.
Back
Top