win32

It works fine with BWC's files. Ximonite made his latest ntdll based on WildBill's ntdll and added all of BWC's functions to it. But it doesn't mix well with BWC's kernel32. And WildBill stopped working on his extended kernel files years ago, so they don't have nearly as much functions as BWC, so they can't run roytam1's browsers.

W7 shouldn't be too difficult, as I think that most system files remain unsigned as in Vista. But I'm not aware of any real software incompatibilities with W10 yet. I'm only aware of the DX12 stuff, UWP stuff, and Office 2019's installer asking for SetCoalescableTimer (Windows 8 and up). XP has One-Core-API.

It still has a long way to go, but I do hope that further updates push it more. Indeed, it doesn't have every function that many Vista display drivers use, and x64 import tables are a pain to deal with. And also digital signatures. Another option is to mod the drivers themselves, where you look at what the incompatible functions do. and compare them with whatever the last compatible version did. BWC has done that, and both approaches may have to be done to get stuff working (pure XP x86 NVIDIA drivers with his extended core have serious problems with some DX9 programs, which are fixed by some of his modded versions).

WSUS Offline Update ESR 9.2.5 (a front end for wsusscn2.cab it appears) still gets most XP x86 and Server 2003 x64 updates as of now. Seemingly, the only thing that fails is WMP11, but that was probably served through the MS Download Center as opposed to Windows Update.

WSUS Offline Update ESR 9.2.5 still gets most of them (WMP11 seems to be gone though): https://download.wsusoffline.net/wsusoffline925.zip

You're the second one who has reported that. I still have it on mine, but that's my main machine with April 2017 updates. Indeed, my VM with July 2020 updates does have this problem. The solution is to make a folder named sidebar.exe.local in Program Files\Windows Sidebar and place your original ole32.dll in there (make sure you applied my reg key). Then it will work.

MS did say that they were shutting down SHA-1 endpoints for Windows Update. So 2000, XP and Vista are dead right there. The SHA-2 updates for Server 2008 came out after the build number changed to 6003, and Windows Update also broke on Vista with the change to 6003, so you're SOL.

Microsoft Update Catalog still has many Windows 2000 updates, so I would have expected that they wouldn't have used the SHA-1 deprecation to dismantle the update infrastructure for a product that will only exit extended support in October. Mobile apps with short clips of people dancing are now more important than Windows and Office to MS.

Realtek 8821CE: https://www.realtek.com/en/component/zoo/category/rtl8821ce-software (the second download link of course!) But the Radeon Vega 8 Mobile: https://www.amd.com/en/support/previous-drivers/apu/amd-ryzen-processors/amd-ryzen-5-mobile-processors-radeon-vega-graphics/amd-ryzen-5-2500u You may still have a chance with 2017 drivers, but wayback machine is broken right now though Why does OS support get dropped for mobile GPUs before desktop ones, anyway? You may want to look at this and inf mod the driver specified: https://community.amd.com/thread/224947 If you try using such a driver, you will probably have to disable driver signing enforcement.

I'm not exactly sure what your hardware is, but I see that you have some kind of AMD graphics. Their newer drivers crash under Windows 8, yet they don't on 8.1. In any event, try finding the drivers on AMD's website. You also seem to have Realtek audio. Vista and up do have an inbox driver so it may not be a problem but it appears their newest stuff will work: https://www.realtek.com/en/component/zoo/category/pc-audio-codecs-high-definition-audio-codecs-software

Is this with HDA devices by any chance? And if so, was KB888111 installed beforehand? I know that something that is in USP 5.1 breaks it, and whatever it is must have been integrated before KB888111 in such a case (it doesn't have to be in USP 5.1, it could be in other things as well). Perhaps it's something originally from XP that expects a non-existent Windows Audio service? audiosrv.dll from 2003 SP2 has no missing functions, so you could export HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Audio from XP/2003 to your win2k, copy audiosrv.dll to system32 and try it out.

He meant offset 34214. And there is a version of sdbus.sys that is 5.1.2600.5512, that you should be able to locate in X:\WINDOWS\system32\drivers (in XP of course). And if it's there then it should be on the install medium, which should allow setup to detect it, in conjunction with the Intel inf. So I do believe that ACPI is a bigger issue than storage controllers.

Presently, only browsers based on Chromium 72 and older run.

You have to replace system files to play YouTube videos with Firefox 78 or 79.

What really surprises me is that Windows 2000's ntdll works with the export table at the end of the file, while putting the export table at the end of a Vista x86 system file breaks it. There is a lot more freedom on Windows 2000 than with other proprietary OSes. And it's only 4 functions away from running Pale Moon 28.11!

While I'm quite satisfied with the progress made thus far, many other kernel extension projects spend years in development (Windows 2000 extended kernel started development in January 2011 with the latest update in August 2019, and is based off the KDW wrapper that was introduced in 2008; even today it doesn't run everything that XP runs) so it may take awhile before it can be considered finalized. The x64 version is quite stable for the programs that run under it, with only a few minor caveats. The DLL redirection method takes care of compatibility issues that arise with programs that ran previously. Things are not as solid on the x86 front and it will take longer to figure it out.

It is unstable and somewhat slow to boot with the EFI loader compared to 2012R2 on a 5400 rpm HDD. About five random services do not start at each boot. This wrecks havoc on Windows Updates, as they often fail and in one case broke the install.

I decided to focus on the x86 stuff while I was away from my Kaby Lake hardware. But I'll be back with it on Sunday.

I tried that, and it failed. Next thing I'm trying is seeing if there are alternate functions that will satisfy the programs; if so, then the new functions will be directed to those. But the AppUserID stuff in the taskbar is quite novel.

The x86 shell32.dll has serious problems, specifically with (Get/Set)CurrentProcessExplicitAppUserModelID. Buffer overflows occur triggering DEP. Even the win2k versions of the functions by BWC has the same problems. So more time will be required to get in working order. I see that the working x64 versions of those functions have some key differences that set them apart from the x86 ones. Not sure if that will help much or not.

Yeah, I had glossed over those "cf" folders. For shell32, I'm on it! I found that "big picture" mode still works quite well, with the store and workshop among others, but it has no search function!

You can use an hex editor like HxD. Search for a sequence of bytes that goes 6A 00 6A 01 6A 06 And change the 6A 01 to 6A 00.

The notion of running new versions of Steam on Vista is not as clear cut as it should be; Application Verifier does not bypass the check. So I looked in steam.exe and found this:

I had trouble finding a Vegas Pro 15 installer from official sources (I found it here: https://dl03.magix.net/trial_vegaspro15_dlm.exe), so I tried Vegas Pro 17. It was going fine but noticed that it made no effort to copy files to the directory and gave the error "setup has completed successfully". Apparently the official minimum requirements are Windows 10 and Skylake even though the installer's version check allows Windows 7. Vegas Pro 15 did the same thing for me. But my .NET 4+ is all messed up anyway. Try looking for logs in X:\Users\User\AppData\Local\Temp and X:\Users\User\AppData\Roaming\Sony and put them here.

The installers are 32bit, even if they install the x64 version.