Search results

  1. B

    Update Win11 22H2 image to 23H2 - How?

    I hate to ask, I figured this would be a common question but it does not seem like it after some digging. I would like to upgrade my image from Win11 22H2 to 23H2. Using the patching inside NTLite doesn't seem to offer this, and I'd rather not spend days trying to rebuild it.
  2. B

    Components return after Windows Update (Content Delivery Manager)

    I don't even mind if it stays in place IMO. I wonder if you made this into a Post-Install User Script if that would fix this: (I see a lot of comments online this works well.) reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager" /v "ContentDeliveryAllowed" /t REG_DWORD...
  3. B

    Components return after Windows Update (Content Delivery Manager)

    Hey all! I know there is a thread on this somewhere, but I've spent quite a bit of time trying to re-find it. I swore someone mentioned a script. I now realize that every time a Cumulative Update is pushed, it will usually replace the removed Components. That means that Content Delivery...
  4. B

    Including winget in NTLite image for Post-Setup installs

    Curious; For the hard-coded path, would it make sense to use $PSScriptRoot?
  5. B

    $OEM$ folder incomplete - Doesn't copy it all?

    Yep! This would be the smarter idea! HAHA d'oh. I hope I can contribute to this group. :) Thanks again garlin :)
  6. B

    $OEM$ folder incomplete - Doesn't copy it all?

    It was there in the log.txt... I'm the bonehead. I didn't want my scripts scattered, so I moved the WinGet scripts into that folder. I usually audit PowerShell I find online before using, and found hard-coded path so I updated that to the folder location. I completely missed the line...
  7. B

    $OEM$ folder incomplete - Doesn't copy it all?

    Oh. OH OH... I just had a thought... I wondering if the SetupComplete.cmd EDIT: cleanup script deletes ANY Scripts folder in $1? EDIT #2: It is contained in a "LocalConfig" folder. I did check, no spaces, no special characters. <drive>:\sources\$OEM$\$1\LocalConfig\Scripts
  8. B

    $OEM$ folder incomplete - Doesn't copy it all?

    I saw that in one of the scripts that Setup\ gets purged. I like to keep around an installer for additional users, for example. Yes, I am using NTFS for the final USB. I've been half tempted to look at chowning $OEM$ or changing my $OEM$ folder permissions.
  9. B

    $OEM$ folder incomplete - Doesn't copy it all?

    Let me describe the process I used more concisely. Decompress ISO to folder on exFAT external SSD (Shouldn't have permission problems) Created $OEM$\ inside of extracted folder's sources\ Created $$\ inside $OEM$\ To customize wallpaper/lock screen Created $1\ inside $OEM$\ To change default...
  10. B

    $OEM$ folder incomplete - Doesn't copy it all?

    I had read that you can drop stuff directly into the sources folder once you decompress the original ISO (It is the way suggested here for changing out desktop wallpaper/Profile icon/lock screen.) It had been working until I started having problems with the Post-Setup. Once I can get back to...
  11. B

    $OEM$ folder incomplete - Doesn't copy it all?

    I have been seeing if NTLite will do what I need. I have butted into a couple of challenges. First, I bumped into that Post-Setup seemed to have corrupted or something in the XML file. This caused a few weird bugs, so I started over. I noticed if you put an argument into a User, and then after...
Back
Top