We have mostly W11 24H2 systems, and we've seen recently an odd or different behavior when applying the LCU via CM/Wsus - systems need 2 reboots to fully apply the LCU. Is that everyone else's experience as well?
We noticed water coming out of the corner of our fridge under the floor, and traced it back to a pool of frozen water, forming on the bottom of our freezer. I can’t see any leak of any sorts. What might be causing this? We’ve pulled everything out just so we could diagnose this, but I’m not seeing anything yet.
My admin account, which is also my CM admin account, has no access to the internet. In the past, when I've tried to install/run the MDM tool, it has to both connect to the CM infra, and connect to the internet - but my admin account is also blocked from accessing the internet. I really don't want to make my standard user account a full CM Admin, what other options do I have, short of asking our security/firewall team to allow comms to specific URLs required by the MDM tool? It's kind of a catch-22.
I’m trying to integrate the latest SSU, LCU, .NET patches, and possibly a few additional KBs related to Secure Boot DBX and microcode updates into some older Windows 10 LTSC images, and I’m looking for advice on best practices.
I found Microsoft’s official guide along with the example script, but it spends a lot of time covering Dynamic Updates. From what I understand, I may not actually need to integrate those, although I could be mistaken.
The guide also includes steps for updating WinRE and WinPE. Is it actually necessary to apply the SSU and LCU to the WinRE image inside the Windows 10 image, or is patching the main OS image enough?
I’m also trying to follow the recommended order of operations as closely as possible while modifying the script for my own workflow. My goal is to end up with:
a fully updated install image
a repeatable script/process I can reuse later.
I’m aware of the excellent work from people here, including the Wimwitch alternative patching script , but most of the discussion seems focused on newer Windows 11 servicing techniques. I’m specifically working with older Windows 10 LTSC images, where things like the ICU update process and Features on Demand ISO layout are a bit different.
Has anyone here built and maintained fully patched Windows 10 LTSC images recently? If so, I’d really appreciate any guidance, recommended workflows, or lessons learned.
Since about the release of the March cumulative updates were released for W11, CM, we’ve been seeing huge increase of failures for W11 language pack installations. We allow users to install the languages via the language and regional UI settings, rather than using a separate package or app deployments. This has been working great for the last few years, until recently- users trigger the install and shortly afterwards they see a hex code error that I can’t remember at the moment. We’re still working on troubleshooting and investigating. Is anyone having similar issues, or aware of any known issues/bugs that affect W11 24H2, with either the March or April LCU?
Update - just to be thorough, I also tested installing the language cabs directly using powershell/dism commands, with the FULL FOD ISO copied to the system, and with 'limitaccess' added to the command lines. I installed all De-de cabs (German), installed, rebooted, went to install the language via settings, saw the download button, but when I click it, it runs for a few minutes then fails! all the other language features installed fine.
We're dipping our toes into the WUFB world, and are trying to piece together how the various techs work together (or not). For those that are already doing this, please let me know how you guys are implementing Windows Update for Biz, Delivery Optimization and Connected Cache, respectively or together. What DO policies are you enabling, are you setting up connected cache servers for each site, are you using CM to monitor any of it, perhaps via the Client Data Sources? Any guides, websites you'd recommend me reading would be great if you could share your sources and experience, thanks! FYI - We're fully SCCM on prem, WSUS, and haven't yet switched to intune, comanagement, etc. but are testing this out as well.
