Autoexe.bat

I have done so and malware sweeps. This file was installed when I installed Widows Seven - new install on a new hard drive. It was there before I ever went online. So it was part of the installation of Ultimate. I have no problem deleting it. NTVDM is an MS file:

Description: File ntvdm.exe is located in the folder C:\Windows\System32. The file size on Windows XP is 520,192 bytes.
It is a Windows core system file. The program has no visible window. The file is a Microsoft signed file. Therefore the technical security rating is 2% dangerous, however also read the users reviews.

Important: Some malware camouflage themselves as ntvdm.exe, particularly if they are located in c:\windows or c:\windows\system32 folder. Thus check the ntvdm.exe process on your pc whether it is pest.

ntvdm.exe

ntvdm.exe known as NT DOS Virtual Machine ntvdm, has the following information and may help up understand this process better.

ntvdm.exe - Here is the scoop on NT DOS Virtual Machine as it pertains to computer network security. The big question: what is ntvdm.exe and is it spyware, a trojan and if so, how do I get rid of NT DOS Virtual Machine?
ntvdm.exe (NT DOS Virtual Machine) - Details

The ntvdm.exe process is used when you run DOS or 16-Bit software on your windows pc. It will emulate the old DOS/16-bit os to allow older programs to run. If you are running DOS based (or 16-bit) programs on your computer, you should leave this process running.
ntvdm.exe is flagged as a system process and does not appear to be a security risk. However, removing NT DOS Virtual Machine may adversly impact your system.
The Process Server database currently registers ntvdm.exe to Microsoft.
This is part of Microsoft Windows (NT).

Therefore I conclude the autoexec.bat was installed by Windows Seven Ultimate and that I do not need it.

CarlTR6 said:

Therefore I conclude the autoexec.bat was installed by Windows Seven Ultimate and that I do not need it.

It is indeed a Windows generated file for 16-bit legacy support.

Realistically, it's best just to leave it alone as it would serve no purpose removing it.

AUTOEXEC.BAT is indeed created by Windows 7 32 bit. Its a dummy placeholder file and it contains only this...

REM Dummy file for NTVDM

For those of you who still remember DOS batch commands, REM stands for REMARK or in other words COMMENTS.

Since the OP says the file is AUTOEXE.BAT and not AUTOEXEC.BAT, it could be something malacious
OR
The OP might have spelt it wrong :)

smarteyeball said:

It is indeed a Windows generated file for 16-bit legacy support.

Realistically, it's best just to leave it alone as it would serve no purpose removing it.

Thanks for the confirmation. I will leave it as it certainly does not hurt anything. And I probably have some old 16 bit games in a box somewhere. :)

unifex said:

I don't have any autoexec.bat in my 7 Ultimate x64! Maybe I did not try anything 16-bit, wait a minute, 16-bit is not supposed to work on x64, maybe that's why.

I forgot about 32 bit vs 64 bit. That would explain it not showing up for most of the Ultimate users here.

gladson1976 said:

AUTOEXEC.BAT is indeed created by Windows 7 32 bit. Its a dummy placeholder file and it contains only this...

REM Dummy file for NTVDM

For those of you who still remember DOS batch commands, REM stands for REMARK or in other words COMMENTS.

Since the OP says the file is AUTOEXE.BAT and not AUTOEXEC.BAT, it could be something malacious
OR
The OP might have spelt it wrong :)

I do well remember the REM command in DOS. I used it frequently in making notes to myself when I edited/created batch files.

captnorm said:

I hate to bring up a dead horse, but would like to run a DOS command each time Windows 7 boots. I come from the old DOS days and have been reading this thread & confirmed AUTOEXEC.BAT definitely doesn't run as part of the boot process in win7. It's a long story, but my backup program doesn't backup a specific file, as truecrypt doesn't update the modified date. I'd like to run a DOS command like "COPY FILE.EXT +" each time Win7 boots, as that command updates the modified date to the the current day.

Can anyone think of another way to modify the date of a file (to be today), each time the system boots?

Thanks,

Norm

I think you can use this small utility to 'touch' the file so that the timestamp is changed.
Touch for Windows - CodeProject

You can create a shortcut for 'touch' in the StartUp folder with the following parameters

Code:

To change the Access Time
touch -a <file path and name>

To change the Created Time
touch -C <file path and name>

To change the Modification Time
touch -m <file path and name>

OR

You can also use this simple utility to change only the modification date/time
Touch.exe: Set the timestamp of files to the current time on Windows systems

Usage is,

Code:

Set the modification date/time of <file> to the current date/time.
touch.exe <file path and name>