search

leecher1337 / ntvdmx64

Run Microsoft Windows NTVDM (DOS) on 64bit Editions
778 stars 80 forks source link

Windows 11 update KB5035942 breaks ntvdmx64 (WIN10 KB50335491 may as well?) #252

Closed kllkradio closed 3 months ago

kllkradio commented 3 months ago

Last night, I installed the 2024-03 Cumulative Update Preview for Windows 11 on my laptop. After the update completed, ntvdmx64 was no longer recognized by the operating system and gave an error message that 16-bit programs are not supported. I tried removing and reinstalling ntvdmx64 and got the same result. There was also an error message as ntvdmx64 was attempting to be installed. I suspect that this issue may also occur when KB50335491 is installed on a x64 Windows 10 computer.

I am using a build that I compiled last October which should be pretty up to date.

I was able to restore ntvdmx64 operation by uninstalling KB50335942.

Brian

leecher1337 commented 3 months ago

Hi, I didn't find mentioned KB number, I only found KB5035942 , do you mean this one? Normally, if updates are out that update a lot of system files, it may take a few days until the symbols are reade on the Microsoft Symbol Server. Until then, the loader cannot resolve the required symbols and will not work properly. Did you check debugview output referring to some symbol resolution errors, maybe? This usually is the most common cause for Windows updates breaking the loader.

kllkradio commented 3 months ago

Yes, KB50335942. It was released yesterday.

Ahhh. So maybe that is the problem. I didn’t have a chance to explore things further.

On Mar 27, 2024, at 9:34 AM, leecher1337 @.***> wrote:

Hi, I didn't find mentioned KB number, I only found KB5035942 , do you mean this one? Normally, if updates are out that update a lot of system files, it may take a few days until the symbols are reade on the Microsoft Symbol Server. Until then, the loader cannot resolve the required symbols and will not work properly. Did you check debugview output referring to some symbol resolution errors, maybe? This usually is the most common cause for Windows updates breaking the loader.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.

kllkradio commented 3 months ago

I reinstalled the update this evening and everything is now working fine.

Brian