[TylerE]

Perhaps the best example I can think of is the whole situation

InstallShield is....massive crapware and actually generated 16 bit installers way way after anyone was using 16bit PCs. Nobody notices until, I think it was W8 or W10 dropped support for running 16bit executables (something about dropping the subsystem that supported them.

[Fulgen]

Nobody noticed because Windows special cased InstallShield.

https://devblogs.microsoft.com/oldnewthing/20131031-00/?p=27...

[dtech]

It was 64-bit Windows versions, 16 bit was never supported not even on XP 64-bit. I think W8 was the first 64-bit only Windows.

[fredoralive]

Windows 11 drops IA32, and thus (first party) MS-DOS and Windows 3.x support.

Windows actually has some special cased support for (at least some of) the problematic 16 bit InstallShield installers to run a 32 bit version instead on AMD64.

[EvanAnderson]

Windows 11 was the first 64-bit only build of the NT-based Windows tree. There are 32-bit x86 builds of all previous versions.

[Wowfunhappy]

> I think W8 was the first 64-bit only Windows.

Nope, that would be Windows 11! There is a 32-bit version of Windows 10.

[Wowfunhappy]

From InstallShield’s perspective, why would they replace working 16-bit code which is still natively compatible with Windows and x86? Because Windows and/or Intel might (or might not) drop support a decade later?