Tripredacus

The forum doesn't keep email address history. It can't show me who had a live.ca email in the past and had since changed it.

No user has registered/used with a live.ca email since 2015 but that email domain is not being blocked by the forum. The issue lies elsewhere.

Not sure about 2000 but for XP you can use WSUS

If the issue is that the image is too big, they can use imagex /export to see if it reduces the filesize. Maybe DISM export does the same thing.

Not going to happen on a ban on rule 1.

We can probably not count Wolfenstein: The New Order at this time as using 3 api files from Windows 8.0 and copying the kernel32.dll from Windows 7 and renaming it as api-ms-win-core-file-l1-2-2.dll allowed the game to actually launch. I was really expecting it to keep asking for more different files to hunt down but glad enough I can actually play this game. So this can be a way to try to get programs to work in Windows 7 but only those programs that aren't doing a hard check on the OS itself. And now my Windows 7 PC has joined the old tradition of my Windows 98 PC as having future OS files in it to run programs it isn't supposed to be running.

I had tried doing this, but the game then complains about missing entry point for GetVolumeInformationA, which if this is correct: "Introduced into api-ms-win-core-file-l1-2-2.dll in 10.0.16299." https://docs.microsoft.com/en-us/uwp/win32-and-com/win32-apis It is the only location. So while my OS may have a GetVolumeInformationA entry in kernel32.dll, the game is not calling that because it is trying to do it with that specific API. And the APIschema is mapped into memory and the file-l1-2-2 is not present at all. This file is one of the few that doesn't actually seem to exist, as it is (was?) mapped to kernerlbase.dll in Windows 10 from its own schema. I do not know if there are any integrity checks that would be done, perhaps having a dummy .dll file present that just redirects the call to kernel32.dll would work but I haven't a clue on where to start. I suppose I could take the kernel32.dll from system32 and put it into the workdir and rename it to core-file-l1-2-2 and see what happens.

I was excited that this would be some magic bullet but alas it only resulted in generating a 0xC000021a bugcheck on reboot. I'd rather not have to bother with that any longer and would prefer to source the file it wants instead. It was not present on my Windows 8.1 test system, nor my Windows 10 workstation. Searching online doesn't easily reveal where the file comes from.

Updated

As I had suspected, there is a rabbit hole involved here. I had made a copy of the entire DLL set from Windows 8 and 8.1 just in case it wanted more. And it did, and I had to put 4 more DLLs from Windows 8 into the working DIR. It still has not opened, as it needs another DLL that I didn't have and will have to see what happens after I find that one. EDIT: the file now missing is api-ms-win-core-file-l1-2-2.dll, which leads me to an interesting post on stackexchange here (just don't read the comments) https://stackoverflow.com/questions/69943334/newer-windows-sdks-cause-api-ms-win-core-file-l1-2-2-dll-missing-on-windows-7-8

I don't even have the moon button anymore.

The build of Wolfenstein: The New Order from Epic Games does not open on Windows 7. It requires a file api-ms-win-core-com-l1-1-0.dll which is said to be in a VCRedist but it is only from Windows 8 (or 10) and does not get installed on Windows 7. I did not try to get this file from a Windows 8 system to see if that allowed it to run or lead to any other message.

The topic title doesn't make any sense.

Alt+Shift will change the input language also.

In my experience, I have never been able to resolve a situation where the OS gets stuck at the boot animation, going back to Vista. The logs you posted (and the logs in general) are not useful in this regard. What is needed is to set the BCD option to enable debug and another machine with windbg installed (as well as the knowledge to use it in this context) to fully determine where the issue is, presuming the debugger catches it. You can find info on this by searching these words in google. windbg boot debug

CSM disabled or not?

We must be clear here and explain that Ubisoft did not announce they were dropping support. They announced they will be actively blocking their program from running on Windows 7. It is a completely different thing.

All of these has been changed. For whatever reason the forum did not show me there were new posts in this thread so I didn't see the ones from May 7 until today.

Me too but I have a sneaking suspicion. Split from wayforward topic.

I have some experience as a user of a Ruffle implementation on another site, specifically the SMF plug-in. It is not perfect and is not good in some instances where you'd be better off using actual Flash instead. The specifics are memory leaks and not being able to handle large amounts of symbols. The symbols one is weird as it causes logic errors to occur.

Yes the BIOS can lock out the ability to boot specific architectures. If this is indeed the issue, the only solution is to get a modified BIOS from the manufacturer. There may be a version already available that allows x86 boot but it wouldn't be the latest. You'll have to look at older BIOS and their changelogs if the manufacturer makes things like that. For example, Intel has release notes for their different versions that can be read to find specific ones to use.

https://msfn.org/board/topic/94976-howto-windows-vista-x86-and-x64-in-the-same-dvd/

Recommend changing topic title to exactly what it is you want, otherwise this thread will draw spambots.

It was a few years ago that the county executive had decided to back some plan to ban plastic bags because one time he was driving in the city, he saw plastic bags stuck to trees. And he then decided that banning the use of plastic bags was the solution and not say... organising some groups to clean up the garbage. And everyone also conveniently forgot the last time we banned plastic bags in the 90s that didn't end up lasting. For one it was the 90s and the alternative was some sort of composite bag made from corn or something that would fall apart or biodegrade way too soon... like still at the store. So they made everyone use paper bags. Then the environmentalists made a big fuss about all of the trees that were being cut for the bags and they went back to plastic. So now that we are back to paper (although many places are still using plastic despite the ban) I am counting the days until the crying over cut trees is heard again.

The issue isn't that simple. The reason is that every program is different and they store files all over the place. I'd rather spend the time using my computers for what I want to, rather than spend countless hours trying to track where a hundred programs write files and see if I can redirect them or not. Basically, I am past those days of hobbyist workings with Windows in that capacity.