C:\WINNT\SYSTEM32\AUTOEXEC.NT Error .Help plz if you can !!

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello community.

I have 3 W2K boxes on my network have developed the above error when trying
to run a educational spelling program. They ran the program fine up until 3
weeks ago.

I have search the net and tried the fix listed below. It cure the problem,
but when the systems are rebooted the problems still prevail :(

Can someone do me a be fav and suggest a long term fix?


">Problem:
During software installation one of the following error appears:


16-bit MS-DOS Subsystem
<executable name>
C:\WINNT\system32\autoexec.nt
The system file is not suitable for running MS-DOS and Microsoft Windows
applications.
Choose 'Close' to terminate the application.

16-bit MS-DOS Subsystem
<executable name>
C:\WINNT\system32\config.nt
The system file is not suitable for running MS-DOS and Microsoft Windows
applications.
Choose 'Close' to terminate the application.

Cause:
If AUTOEXEC.NT, CONFIG.NT or COMMAND.COM are missing from
%SystemRoot%\System32 folder, or if they have been improperly modified, these
messages may occur. See Microsoft tech note
http://support.microsoft.com/default.aspx?scid=kb;en-us;305521 for details.

Solution:

Default versions of these files can be found on the Windows installation CD.
The following instructions will work if your Windows directory is "C:\WinNT".
If it is something else, you will need to substitute your Windows directory.
The example commands also assume that the CD drive is drive D:. If your CD
drive has a different drive letter, use that letter instead of D:\.
1. Insert the Windows CD in the CD drive
2. Open a command prompt by clicking the Windows start button and selecting
Run, typing CMD and pressing the Enter key.
3. Execute the following commands from the command prompt:


EXPAND D:\i386\autoexec.nt_ C:\WinNT\system32\autoexec.nt
EXPAND D:\i386\config.nt_ C:\WinNT\system32\config.nt
EXPAND D:\i386\command.co_ C:\WinNT\system32\command.com

4. To close the command prompt, type EXIT and press the Enter key.
Related Links:

"<

Thanks for any assistance.

ppls
 
AUTOEXEC.NT Fix Method 1:
copy; %windir%\repair\autoexec.nt
to
%windir%\system32


AUTOEXEC.NT FIX Method 2:
Go to; Start --> Run
enter; cmd.exe

{ assuming the Win2K CDROM disk is in drive "D:" }
In the Command Prompt enter...
expand D:\i386\autoexec.nt_ %windir%\system32\autoexec.nt


Since there are many forms of malware that can cause a problem with AUTOEXEC.NT, please
perform the following...


1) Download the following three items...

Trend Sysclean Package
http://www.trendmicro.com/download/dcs.asp

Latest Trend Pattern File.
http://www.trendmicro.com/download/pattern.asp

Adaware SE (free personal version v1.05)
http://www.lavasoftusa.com/

Create a directory.
On drive "C:\"
(e.g., "c:\New Folder")
or the desktop
(e.g., "C:\Documents and Settings\lipman\Desktop\New Folder")

Download Sysclean.com and place it in that directory.
Download the Trend Pattern File by obtaining the ZIP file.
For example; lpt371.zip

Extract the contents of the ZIP file and place the contents in the same directory as
sysclean.com.

2) Update Adaware with the latest definitions.
3) Reboot your PC into Safe Mode
4) Using both the Trend Sysclean utility and Adaware, perform a Full Scan of your
platform and clean/delete any infectors/parasites found.
(a few cycles may be needed)
5) Restart your PC and perform a "final" Full Scan of your platform using both the
Trend Sysclean utility and Adaware

* * * Please report your results ! * * *

--
Dave
http://www.claymania.com/removal-trojan-adware.html



| Hello community.
|
| I have 3 W2K boxes on my network have developed the above error when trying
| to run a educational spelling program. They ran the program fine up until 3
| weeks ago.
|
| I have search the net and tried the fix listed below. It cure the problem,
| but when the systems are rebooted the problems still prevail :(
|
| Can someone do me a be fav and suggest a long term fix?
|
|
| ">Problem:
| During software installation one of the following error appears:
|
|
| 16-bit MS-DOS Subsystem
| <executable name>
| C:\WINNT\system32\autoexec.nt
| The system file is not suitable for running MS-DOS and Microsoft Windows
| applications.
| Choose 'Close' to terminate the application.
|
| 16-bit MS-DOS Subsystem
| <executable name>
| C:\WINNT\system32\config.nt
| The system file is not suitable for running MS-DOS and Microsoft Windows
| applications.
| Choose 'Close' to terminate the application.
|
| Cause:
| If AUTOEXEC.NT, CONFIG.NT or COMMAND.COM are missing from
| %SystemRoot%\System32 folder, or if they have been improperly modified, these
| messages may occur. See Microsoft tech note
| http://support.microsoft.com/default.aspx?scid=kb;en-us;305521 for details.
|
| Solution:
|
| Default versions of these files can be found on the Windows installation CD.
| The following instructions will work if your Windows directory is "C:\WinNT".
| If it is something else, you will need to substitute your Windows directory.
| The example commands also assume that the CD drive is drive D:. If your CD
| drive has a different drive letter, use that letter instead of D:\.
| 1. Insert the Windows CD in the CD drive
| 2. Open a command prompt by clicking the Windows start button and selecting
| Run, typing CMD and pressing the Enter key.
| 3. Execute the following commands from the command prompt:
|
|
| EXPAND D:\i386\autoexec.nt_ C:\WinNT\system32\autoexec.nt
| EXPAND D:\i386\config.nt_ C:\WinNT\system32\config.nt
| EXPAND D:\i386\command.co_ C:\WinNT\system32\command.com
|
| 4. To close the command prompt, type EXIT and press the Enter key.
| Related Links:
|
| "<
|
| Thanks for any assistance.
|
| ppls
 
Hello David,

Can i just ask:

with Fix 1.
AUTOEXEC.NT Fix Method 1:
copy; %windir%\repair\autoexec.nt
to
%windir%\system32

is the %windir%\repair\autoexec.nt located on the CD?

Will Trend have any effect on Sophos that is running?

Thanks gain and i'll try your tips next week when i am back on that site.

I'll report back then.

tx

ppls
 
No.

%windir% is an environmental variable and on Win2K USUALLY points to c:\winnt
so it would be...

Copy;
c:\winnt\repair\autoexec.nt
to
c:\winnt\system32

Trend Sysclean is a utility and will only work if you manually execute SYSCLEAN.COM and
happy exist on a Sophos equipped platform.

--
Dave




| Hello David,
|
| Can i just ask:
|
| with Fix 1.
| AUTOEXEC.NT Fix Method 1:
| copy; %windir%\repair\autoexec.nt
| to
| %windir%\system32
|
| is the %windir%\repair\autoexec.nt located on the CD?
|
| Will Trend have any effect on Sophos that is running?
|
| Thanks gain and i'll try your tips next week when i am back on that site.
|
| I'll report back then.
|
| tx
|
| ppls
|
|
|
| "David H. Lipman" wrote:
|
| > AUTOEXEC.NT Fix Method 1:
| > copy; %windir%\repair\autoexec.nt
| > to
| > %windir%\system32
| >
| >
| > AUTOEXEC.NT FIX Method 2:
| > Go to; Start --> Run
| > enter; cmd.exe
| >
| > { assuming the Win2K CDROM disk is in drive "D:" }
| > In the Command Prompt enter...
| > expand D:\i386\autoexec.nt_ %windir%\system32\autoexec.nt
| >
| >
| > Since there are many forms of malware that can cause a problem with AUTOEXEC.NT, please
| > perform the following...
| >
| >
| > 1) Download the following three items...
| >
| > Trend Sysclean Package
| > http://www.trendmicro.com/download/dcs.asp
| >
| > Latest Trend Pattern File.
| > http://www.trendmicro.com/download/pattern.asp
| >
| > Adaware SE (free personal version v1.05)
| > http://www.lavasoftusa.com/
| >
| > Create a directory.
| > On drive "C:\"
| > (e.g., "c:\New Folder")
| > or the desktop
| > (e.g., "C:\Documents and Settings\lipman\Desktop\New Folder")
| >
| > Download Sysclean.com and place it in that directory.
| > Download the Trend Pattern File by obtaining the ZIP file.
| > For example; lpt371.zip
| >
| > Extract the contents of the ZIP file and place the contents in the same directory as
| > sysclean.com.
| >
| > 2) Update Adaware with the latest definitions.
| > 3) Reboot your PC into Safe Mode
| > 4) Using both the Trend Sysclean utility and Adaware, perform a Full Scan of your
| > platform and clean/delete any infectors/parasites found.
| > (a few cycles may be needed)
| > 5) Restart your PC and perform a "final" Full Scan of your platform using both the
| > Trend Sysclean utility and Adaware
| >
| > * * * Please report your results ! * * *
| >
| > --
| > Dave
| > http://www.claymania.com/removal-trojan-adware.html
| >
| >
| >
| > | > | Hello community.
| > |
| > | I have 3 W2K boxes on my network have developed the above error when trying
| > | to run a educational spelling program. They ran the program fine up until 3
| > | weeks ago.
| > |
| > | I have search the net and tried the fix listed below. It cure the problem,
| > | but when the systems are rebooted the problems still prevail :(
| > |
| > | Can someone do me a be fav and suggest a long term fix?
| > |
| > |
| > | ">Problem:
| > | During software installation one of the following error appears:
| > |
| > |
| > | 16-bit MS-DOS Subsystem
| > | <executable name>
| > | C:\WINNT\system32\autoexec.nt
| > | The system file is not suitable for running MS-DOS and Microsoft Windows
| > | applications.
| > | Choose 'Close' to terminate the application.
| > |
| > | 16-bit MS-DOS Subsystem
| > | <executable name>
| > | C:\WINNT\system32\config.nt
| > | The system file is not suitable for running MS-DOS and Microsoft Windows
| > | applications.
| > | Choose 'Close' to terminate the application.
| > |
| > | Cause:
| > | If AUTOEXEC.NT, CONFIG.NT or COMMAND.COM are missing from
| > | %SystemRoot%\System32 folder, or if they have been improperly modified, these
| > | messages may occur. See Microsoft tech note
| > | http://support.microsoft.com/default.aspx?scid=kb;en-us;305521 for details.
| > |
| > | Solution:
| > |
| > | Default versions of these files can be found on the Windows installation CD.
| > | The following instructions will work if your Windows directory is "C:\WinNT".
| > | If it is something else, you will need to substitute your Windows directory.
| > | The example commands also assume that the CD drive is drive D:. If your CD
| > | drive has a different drive letter, use that letter instead of D:\.
| > | 1. Insert the Windows CD in the CD drive
| > | 2. Open a command prompt by clicking the Windows start button and selecting
| > | Run, typing CMD and pressing the Enter key.
| > | 3. Execute the following commands from the command prompt:
| > |
| > |
| > | EXPAND D:\i386\autoexec.nt_ C:\WinNT\system32\autoexec.nt
| > | EXPAND D:\i386\config.nt_ C:\WinNT\system32\config.nt
| > | EXPAND D:\i386\command.co_ C:\WinNT\system32\command.com
| > |
| > | 4. To close the command prompt, type EXIT and press the Enter key.
| > | Related Links:
| > |
| > | "<
| > |
| > | Thanks for any assistance.
| > |
| > | ppls
| >
| >
| >
 
I believe it is AV software that is causing this. This newsgroup has undergone an exceptional amount of these issues in the last month or so. I read somewhere it could also be a result of AV software.
 
I have heard a similar claim, but only tied to WinXP and AVAST -- so far....

But, on the other hand, there are definitely malware using AUTOEXEC.NT as an execution
vector. It seems to be more prevalent under WinXP. I had a LAN user who didn't practice
Safe Hex and she was infected with non-viral malware that included Blazefind. While I
cleaned her platform, I never narrowed down what was screwing with AUTOEXEC.NT.

--
Dave




I believe it is AV software that is causing this. This newsgroup has undergone an
exceptional amount of these issues in the last month or so. I read somewhere it could also
be a result of AV software.
 
Somehow its practice is to delete that file at startup. I don't understand the significance of this unless it is just supposed to kill their Win16 subsystem. I don't know. It's a strange influx of this issue that's for sure. What they can try to do is remove ALL permissions for it and then reboot and see if it disappears again. Likely not but they might get a Server Management error at boot and track it to what fired the call to autoexecnt.
 
Hello all.

I have tried everything suggested in this post but the problem is solved
ONLY until you either you logo off or reboot the workstation. The the problem
is straight back. :(

Can anyone else suggest a perminate fix??

Thanks for any further assistance.

Ppls

George Hester said:
Somehow its practice is to delete that file at startup. I don't understand the significance of this unless it is just supposed to kill their Win16 subsystem. I don't know. It's a strange influx of this issue that's for sure. What they can try to do is remove ALL permissions for it and then reboot and see if it disappears again. Likely not but they might get a Server Management error at boot and track it to what fired the call to autoexecnt.
Click to expand...
 
Hi Peoples - Try this fix, courtesy of MVP Kelly Theiriot:


"This installaton program will reinstall the missing or corrupt Windows XP
system files command.com, autoexec.nt and config.nt. The absence or
corruption of one or more of these files causes a "16 Bit Subsystem" error.

XP_Fix.EXE by TRF Systems, Inc.
http://www.visualtour.com/downloads/xp_fix.exe

More info here:

Error Message: MS-DOS or 16-bit Windows-based program
http://www.kellys-korner-xp.com/xp_m.htm#16bit"


Then, courtesy of flrman1, here:
http://forums.techguy.org/archive/index.php/t-280212.html

"First in safe mode click on My Computer then click Tools > Folder Options.
In Folder options click on the View tab. Under Files and Folders tick "Show
hidden files and folders" then uncheck "Hide file extensions for known file
types" and uncheck "Hide protected operating system files (recommended)".
Now click "Like current folder" then "Apply" and "OK"

Now find and delete these files:

C:\WINNT\system\windupdate.exe (added by JB: note the spelling - the
added 'd')
C:\WINNT\system.css

Delete this folder:

c:\freescan

Also in safe mode navigate to the C:\Windows\Temp folder. Open the Temp
folder and go to Edit > Select All then Edit > Delete to delete the entire
contents of the Temp folder.

Go to Start > Run and type %temp% in the Run box. The Temp folder will open.
Click Edit > Select All then Edit > Delete to delete the entire contents of
the Temp folder.

Finally go to Control Panel > Internet Options. On the General tab under
"Temporary Internet Files" Click "Delete Files". Put a check by "Delete
Offline Content" and click OK. Click on the Programs tab then click the
"Reset Web Settings" button. Click Apply then OK.


Empty the Recycle Bin"


Run the fix file again after you're done w/the above.

--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP



In
 
This method all refers to Win XP boxes, Mine are 2K pro Boxes. Will this fix
still work/. Have youtried it?

Thanks for another avenue to explore.

Anyone else have a view on my probs or above suggested solution.

Again i thank you..

ppls
 
Hi Peoples - Well, the fix will run on Win2k, but I'm not sure if it's smart
enough to know where to find/replace these on a Win2k box (use %windir%
instead of Windows, etc. and/or on a different partition). We need to ping
Kelly on that one. I would just do the manual replacements per the
Microsoft article,
http://support.microsoft.com/default.aspx?scid=kb;en-us;305521, but also do
the flrman1 fix appropriately adjusted for partition as well and then verify
that things now remain fixed.

--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP



In
 
If you remove ALL permissions on the file it ain't going nowhere. When I say ALL I mean ALL.

--
George Hester
_________________________________
PeOpLeS said:
Hello all.

I have tried everything suggested in this post but the problem is solved
ONLY until you either you logo off or reboot the workstation. The the problem
is straight back. :(

Can anyone else suggest a perminate fix??

Thanks for any further assistance.

Ppls
Click to expand...
 
Back
Top