thepwrtank18

Is it possible to make a custom ISO from a Windows XP installation that was sysprepped, like how you can export an installation to a WIM in Vista and later?

Microsoft-made themes are formatted like this: [name of theme] (folder) - DesktopBackground (folder) - [backgrounds].jpg - icon.jpg - [name of theme].theme - [audio files].wav The problem is, if they're all in the same folder in Windows\Resources\Themes, the file names conflict. I'm making an ISO with everything Microsoft made. All language packs, all updates (2009-2020), and every other "miscellaneous" thing that Microsoft had at some point.

I downloaded every Microsoft-published theme for Windows 7. Is there a way to preinstall the themes onto the offline image with DISM and/or using Audit Mode and Sysprep?

Confirmed working on 26200.5001.

New insider build - 26200.5001

Assuming the theory is true, I'm surprised that they would even bother to flag them as "compatibility issues", making them look like "the bad guys" here. They could have easily said nothing and made Tihiy deal with the mess with no warning, plus avoiding any PR risk along the lines of "why is Microsoft controlling what software I use". Maybe someone at Microsoft actually cares about the quality of the start menu ¯\_(ツ)_/¯

I have a big suspicion they're going to remove the Windows 10 taskbar completely by the release of 24H2. They're just flagging anything using them as "compatibility issues" early, sort of as a warning.

It's completely arbitrary. You can uninstall SAB, update, change the filename of the setup exe to get rid of "startallback", and it works perfectly.

On the bright side, at least SAB has it's own fwlink: https://go.microsoft.com/fwlink/?LinkId=2264757

StartAllBack appears to work just fine with the newest build, despite "compatibility warnings". Kinda shady on MS's part.

Microsoft doesn't allow you to install it.

0xc1900101 is an unrelated issue. MS screwed up the bootloader for the new installs, so it just keeps reverting.

StartAllBack is being intentionally blocked by Microsoft in the latest Canary/Dev update (26100.1). Or it's automatic, who knows.

Can reproduce, same issue here.

xpmgr is a license manager for Windows XP and Server 2003 (and hopefully Office and PLUS!), inspired by slmgr for Windows Vista and newer. It can: Get the system's product ID Change the system's product key Generate an Installation ID Send a Confirmation ID Get the # of days until activation is required Get the # of days until the evaluation period expires, for evaluation copies of Windows https://github.com/UMSKT/xpmgr Credits to diamondggg for making the magic numbers, ICOMLicenseAgent interface, and LoadLicenseManager() function, which were taken from [REDACTED] and modified to work in a CLI. This tool supports all x86 and x64 editions of Windows XP, Server 2003 and other one-off editions. Itanium editions are not supported, as they don't have Windows Product Activation in the first place. This tool does not facilitate piracy. This tool is made for power users to have an easier time with license management on older versions of Microsoft products, before Microsoft made slmgr. All that xpmgr does is use API's that the OOBE (or Office's first run) uses.