AutoPatcher Forum

Hello everyone

When running AutoPatcher, I get errors stating "The NTVDM CPU has encountered an illegal instruction". I then click on "Ignore" and AutoPatcher continues

Any ideas?

Thank you

please, can you give more details about the OS, patch level, etc about your system?

thanks

[]s

In doing a guick Google search, finding alot of references to a similar error possibly being cause by spyware/malware issues on the computer. Don't know what antivirus/spyware rmvl program you are using; but, you may want to try downloading/updating Malwarebytes. Do a full scan and cure any issues, and then see if you can load AP uneffected.

http://www.malwarebytes.org/ , select the free version on the left side of the page.

Other problems relate to possible hardware issues... possibly drivers? But, think this would be a 16-bit program/driver??? Unusuall for WinXP or later. Think Windows uses 3 files to run alot of 16bit programs in compatibility type mode....

http://support.microsoft.com/kb/314106

However, if you don't want to troubleshoot for these issues, it just alot easier to replace the existing 3 files with known good ones.

http://www.tech-pro.net/howto_017.html

Good Luck

Thank you for the replies.

I am running Windows XP Pro SP3 32-bit. I scanned the notebook for malware/viruses, but none were found. I checked the autoexec.nt and config.nt files, and they contain the info per the Microsoft website.

I still get the same error when using AutoPatcher. The problem is reproducible by selecting the "Update for Root Certificates 11/2009 (KB931125)" Critical update. As soon as I click on Next the following error pops up:

16 bit MS-DOS Subsystem
C:\WINDOWS\system32\cmd.exe
The NTVDM CPU has encountered an illegal instruction.

I ran rootsup.exe from the modules\Critical\RootCert_files folder, and it is the culprit giving the error

Kenjutsu, on 26 January 2010 - 09:52 AM, said:

Found the problem: The file was corrupt, so I downloaded it again, and everything worked fine

the issue is in your windows install, not autopatcher. googling your issue, try check the interminable list of results or at least this one

[]s

Cristiano, on 26 January 2010 - 10:14 AM, said:

Just to confirm, the problem is not with AutoPatcher, but with the file that was downloaded from the Microsoft Update site. That file became corrupt, and when I downloaded it manually, and copied it into the correct folder, AutoPatcher worked perfectly.