Search results

I'm trying to find the component, it's called microsoftwindows.client.aix and it's somewhere in the compatibility settings?

Ok, I'm at that screen but unsure which section microsoftwindows.client.aix is under.

Which section is that, I can't seem to find it?

Ok, so probably this one and not one of the features? microsoftwindows.client.aix 'Windows Copilot (Windows Feature Experience Pack)

I accidently removed them but I'm not sure which component it was, my xml is attached.

I also had this option in the settings, but it still shows as pacific time zone. Windows localization > Shell options > Time zone: UTC -5 eastern time

Got it working with the latest ntlite build

I've attached my xml file - I think one of the settings I adjusted must be blocking this, I can't toggle on location services or manually change the time zone. https://imgur.com/a/CtBWxPF

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?

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...

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...

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...

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.

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.

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?

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: https://drive.google.com/file/d/18y1u2vA7cVVs39T5nke-t3edeUeUbJx5/view?usp=sharing

Ok, so send you a CBS log before or after updating the MS ISO?

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...

Ok, update it before sending CBS logs? There was a bug on the initial 24H2 where it would fail sfc, I'm using this iso: https://www.microsoft.com/en-gb/software-download/windows11

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?