Tech Support Forum banner
Status
Not open for further replies.

[SOLVED] Command prompt Accident

841 views 7 replies 4 participants last post by  TazManiac09 
#1 ·
My question reguarding a potential command prompt error.

I recently installed a game that was ment to be played only on Windows xp.
The problem was since vista was unable to run it, i decided to look around forums to see if there was anything i can do to fix this.

I finaly found a command that bypassed the "Data Execution prevention"
Known as:
bcdedit.exe /set {current} nx AlwaysOff

I inserted it in the command prompt and pressed enter.
The game still wouldnt run.
Finally i decided to just uninstall it.

Moments later, i tried running yahoo messenger.
I recieved a message saying "To help protect your computer, Data execution prevention has closed Yahoo messenger.

Not only Messenger but a few other programs as well.

Is there a way to fix this back to normal?

*Ive already tried using:
bcdedit.exe /set {current} nx AlwaysOn

*Shut down, and start up again.

*
 
See less See more
1
#6 ·
Re: Command prompt Accident

Hi, you know there is an old adage that says if you do not know what you are doing don't do it. Ask before you jump. System restore, you will need to put a check next to the Partion1_ C: this will give you restore points in the future on that drive TOO late now I am afraid.

Now your command you have included {current} and there aren't any so DEP remains off (your screen shot shows it greyed out) try this first go to start all programs accessories and right click on "command prompt" select "run as administrator" now type:-

Code:
bcdedit.exe /set nx AlwaysOn
Press enter reboot to take effect

Now if this fails go back to command prompt as above and type:-

Code:
bcdedit.exe /set nx OptIn
Please, before you do something you are not sure about post here, we will gladly help. Good Luck post back so we know how you got on.
 
#7 ·
Re: Command prompt Accident

All my programs are working fine now.
All i did was turn of my pc, and turn it back on the next day.
I stoped messing with the command prompt, and it fixed itself.

Thank you for the help though. Ive learned my lesson.
 
Status
Not open for further replies.
You have insufficient privileges to reply here.
Top