Roy,
That’s actually a useful clue: you do have “MSXML 4.0 SP2 Parser & SDK” installed (so the runtime isn’t totally absent), but FSX Acceleration’s activation is still failing at launch with the generic 0x80004005 “Unexpected error…” message. That usually points to one of two things:
- MSXML4 is installed but not registering/accessible the way the Acceleration activation component expects (often 32-bit registration), or
- something in Windows is blocking the activation/registration UI even though the install itself completed.
Let’s go at it in a clean, step-by-step way.
1) Verify the MSXML4 DLL is really present in Windows folders
Even if it shows in Apps, the real test is whether the DLL exists where Windows loads it from.
Please check these two exact paths and tell me which ones contain msxml4.dll:
C:\Windows\System32\msxml4.dll
C:\Windows\SysWOW64\msxml4.dll
(Yes, it’s counterintuitive: on 64-bit Windows, SysWOW64 is where 32-bit system DLLs live, and FSX/Acceleration is heavily 32-bit.)
2) Re-register MSXML4 properly (both 64-bit and 32-bit regsvr32)
On 64-bit Windows there are two regsvr32’s, and you want to hit the right one for each DLL.
Open Command Prompt as Administrator and run these exactly (some may fail if the matching DLL isn’t present — that’s ok, just report the message):
C:\Windows\System32\regsvr32 C:\Windows\System32\msxml4.dll
C:\Windows\SysWOW64\regsvr32 C:\Windows\SysWOW64\msxml4.dll
Then reboot once and try launching FSX again.
3) Check Windows Security “Protection history” (this catches silent blocks)
Even with “virus programs off”, Windows 11 can still block older activation/registration components without making it obvious.
- Open Windows Security
- Go to Protection history
- Look for anything blocked/quarantined right around the time you launched FSX and got the activation error
If you see anything related to FSX/Acceleration/activation, post the entry details (what was blocked and the path).
4) Run an Acceleration Repair after MSXML4 registration
Once MSXML4 is confirmed/registered, don’t just keep launching FSX.
- Insert Acceleration DVD
- Right-click setup.exe -> Run as administrator
- Choose Repair if it’s offered
- Reboot
- Launch FSX and see if the key prompt returns
A couple quick clarifiers (so I don’t steer you wrong)
- When you said “In Program Files X64 I got File MSXML 4.0 …”, what is the exact full path to that MSXML folder/file you’re seeing? (Please paste it.)
- Do you have FSX installed to
C:\FSX\ (still), or did it end up under Program Files / Program Files (x86) on this Win11 machine?
- When you run the two
regsvr32 commands above, what exact messages do you get back for each one?
Once I know whether msxml4.dll exists in System32/SysWOW64 and what regsvr32 reports, we’ll know immediately if this is an MSXML4 registration/bitness issue or a Windows security block.