SFC /verifyonly - Integrity violations (W11 24H2)

OK, I also had SFC errors after updating it, details above in the same post.

Make sure not to run the SFC scan twice or the log might contain the second, clean result only.

Also DISM Update Cleanup might play a role, it is also automatically started on idle in the installed machine.
 
innovateusa said:
Ok, so send you a CBS log before or after updating the MS ISO?
Click to expand...
Both, if there is any mentioned bluetooth error, then it's confirmed and we can ignore those.
Then focus on non-Bluetooth logs after the removals.
 
Ok, installed the stock Microsoft ISO and got the integrity violation error as expected. Attached are screenshots of the integrity error, and then coming up clean after running Windows update. The CBS log is here:

CBS-Microsoft pre-update.log

drive.google.com drive.google.com
 
It's there, same as mine:
"DEPLOY [Pnp] Corrupt file: C:\WINDOWS\System32\drivers\bthmodem.sys"

So can we now move forward?
Let me know if you get any such errors in the log that are not in this post due to Windows themselves.
 
Sure, any thoughts on what component in the preset is causing it? Maybe I should make one with only packages removed and no setting changed to see if that passes?
 
I'm digging back into this, so you you think it's a setting change not package removal that triggered it? I'll go ahead and make a new iso with only those packages removed to confirm, then start changing one setting at a time until I find which one was the culprit.
 
innovateusa said:
I'm digging back into this, so you you think it's a setting change not package removal that triggered it? I'll go ahead and make a new iso with only those packages removed to confirm, then start changing one setting at a time until I find which one was the culprit.
Click to expand...
No, you and I have proven it's a Windows bug, with or without NTLite.
 
nuhi said:
No, you and I have proven it's a Windows bug, with or without NTLite.
Click to expand...
I'm lost again - we proved that it only happens when making certain package and setting changes - we just need to find which ones triggered it.
 
innovateusa said:
I'm lost again - we proved that it only happens when making certain package and setting changes - we just need to find which ones triggered it.
Click to expand...
It's simple, read your own post above (link).
Check the log.
 
Sorry, your really gonna have to explain this like I'm 5, I'm completely missing the answer, is my logic off here somehow?
1. MS_iso = no sfc error
2. MS_iso w/ your Gaming profile = no sfc error
3. MS iso w/ your Gaming profile + additional packages remove + additonal setting changed = sfc error

My logic says what changed on step 3 must have caused it.
 
innovateusa said:
Sorry, your really gonna have to explain this like I'm 5, I'm completely missing the answer, is my logic off here somehow?
1. MS_iso = no sfc error
2. MS_iso w/ your Gaming profile = no sfc error
3. MS iso w/ your Gaming profile + additional packages remove + additonal setting changed = sfc error

My logic says what changed on step 3 must have caused it.
Click to expand...
1. In your post you stated "installed the stock Microsoft ISO and got the integrity violation error as expected."
Unless the "stock ISO" means "edited ISO", you have confirmed the same result without editing.

Also I have tested and found the same SFC errors in the log without NTLite, not sure why I need to keep on repeating this like you don't believe me or something.
It's in my interest to know the truth, this is not about opinions.
 
I only get the sfc error when I do the additional packages & settings- that's why I think that's the cause. It passes with no problems beforehand.
So you have found the same right- you also get no sfc until you removed the same additional packages and changed the settings. I'm just failing to see how since those were the only chances, they wouldn't be related. It seems like since they are the only changes - it has to be the cause.
 
Please don't twist my words, I was quite clear:
"I have tested and found the same SFC errors in the log without NTLite"
same like you
"installed the stock Microsoft ISO and got the integrity violation error as expected."
 
I'm not trying to twist your words, I'm just trying to figure out which package removal is causing this sfc failure. Is there a more clear way I can say it?

So you get SFC errors with gamer profiles but I don't, that does seem odd since it should be the exact same gamer profile. I guess we must have different gamer profiles/ntlite builds/base iso if we are doing the exact same thing with different results? What data do you need from me?
 
innovateusa said:
I'm not trying to twist your words, I'm just trying to figure out which package removal is causing this sfc failure. Is there a more clear way I can say it?
Click to expand...
There is no package, image without changes has the same log as what you posted above, we both proven it's not any change that causes it.
 
Ok, so it's a setting not a package then? Shall I start testing iso's again to confirm? Any idea of what setting or I'll just start disabling half and making a new iso each time?
 
innovateusa said:
Ok, so it's a setting not a package then? Shall I start testing iso's again to confirm? Any idea of what setting or I'll just start disabling half and making a new iso each time?
Click to expand...
There is no setting, image without changes has the same log as what you posted above, we both proven it's not any change that causes it.
 
You must log in or register to reply here.
Back
Top