Hey all, Scince installing Windows 7 (build 7100) i have noticed that i cannot run batch files, i have checked the coding and even had my friend to look at it and he agrees that @echo off echo YAY it works! pause exit should work... I then relised that i also cannot open CMD. This is very weird and annoying. I double click on the CMD icon in Start>allprograms>accesories>CommandPromt And nothing at all happens. I like windows 7 and would prefer not to go back to vista until my trial runs out, but if this problem cannot be fixed then i might as well go back as i need to be able to run batch files. What can i do to fix this? P.S= I Have a HP Pavillion DV5 1108ax AMD Turion x2 Dual Core Mobile Processor (2.0GHz(1MB L2 Cache)) 15.4 Diagonal WXGA HD Bright-View Widescreen Display 250GB (5400RPM) Hard Drive 2048MB DDR2 SDRAM (1 Dimm) 802.11a/b/g/n WLAN Lightscribe Super Multi 8X DVD+/-RW With Double Layer Support ATI Mobility Radeon HD 3450 Graphics (256MB DDR2 Dedicated Graphics Memory) Used to run Windows Vista (32-bit) Now running Windows 7 32-Bit (Build 7100)

Can't reproduce your problem. I made a "test.bat" with your examples, and it works as ever since my first IBM PCDOS. Command Prompt is accessible and works (you could try to type "cmd" at the search bar, that works, too). Perhaps you could explain more details on what you tried to do, what failed, etc.?Mobile AMD64 3000+, VIA Apollo K8T800 chipset, 1 G RAM, ATIRadeonMobility 9700, 20x DVDRW, C:XPSP3 (55G),D:WIN7 (25G),F:DATA (250G)

Hey, Yeah its really strange... Have a look at this video it will explain how i do it and what it does. http://www.youtube.com/watch?v=ZV3kagu6QsY Cheers, Nick Cyberbeat International www.cyberbeatinternational.com

Nice video, indeed. One notes the professional hand... The only clue I can think of at the moment is that somehow you (or a software, or an administrator) disabled the execution of cmd.exe and batch files intentionally. Look at the registry, HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\System. If there is a key DisableCMD with a value of 2, that would prevent you of doing both of the above. If that's the case, just delete the key.Mobile AMD64 3000+, VIA Apollo K8T800 chipset, 1 G RAM, ATIRadeonMobility 9700, 20x DVDRW, C:XPSP3 (55G),D:WIN7 (25G),F:DATA (250G)

CyberbeatInternational - Hmmm.. Most peculiar indeed. A bit more information, if you can - 1.) 32 bit or 64 bit?2.) In the video, at the very begining, there's a balloon popping up in the right hand side - what's it say?3.) Is this computer part of a domain?4.) If so, do you have any group policies enabled that could possibly be interfering?5.) Were you ever able to run a batch file or launch the CMD prompt? 6.) If so, do you know about when it stopped working - and if so what you were doing just prior to that?7.) If you know about when it stopped working, any chance of doing a system restore to that point in time?P.S. Love that theme!

How was Win 7 installed? Clean or was it an upgrade to Vista or Win7.7000 (or 70xx)? On both 32bit and 64bit versions via a stand alone workgroup or as a member of a domain, I have not had any issues at all.As others have suggested, if you are on a domain, there may be policies in place to prevent running of command prompt and batch files in place.As an example. open gpedit.msc. Navigate to User Configuration --> Admnistrative Templates --> System. There you will see the policy named "Prevent access to the command prompt." It's description reads as below:Prevents users from running the interactive command prompt, Cmd.exe. This setting also determines whether batch files (.cmd and .bat) can run on the computer. If you enable this setting and the user tries to open a command window, the system displays a message explaining that a setting prevents the action. Note: Do not prevent the computer from running batch files if the computer uses logon, logoff, startup, or shutdown batch file scripts, or for users that use Remote Desktop Services.If this is enabled at the domain level, then that explains your issue.

Darien - Long time no see! Welcome back!That policy you mentioned is also available for the local group policy as well.

Thanks for the quick responses everyone, i was expecting to be waiting for weeks! I am currently not at home so i will check the Registry when i get home! Cheers Nick

Hey Wolfie2k6, 1- I believe it is the 32 bit Windows 7. 2- the pop is from Camtasia (Screen Recording software) it just says stuff about what key to press to stop recording. 3- No, this computer is not part of a domain. 4- "" 5- I dont really Know to be honest, i never really tried to open CMD, i just expected that it would when i needed it. 6- "" 7- "" Cheers Nick

Hey DarienHawk67, The computer is not part of any domain, and i just upgraded from Windows Vista 32-bit to Windows 7 (build 7100). I will still have a look at your solution, Cheers Nick.

Haha, i was wondering what to do as i was recording so thats why i was .... Jumpy... Lol. I will look in the registry for that, Cheers Nick

Nick - Hmm.. OK.. Should be pretty much a standard Windows installation.I'd check Darien's suggestion - open GPEDIT.MSC and check the local policy group to see if the "Prevent acces to Command Prompt" items been enabled somehow. If so, disable it, reboot and see if that cures the problem.

Hey all, I had a look in my directory and nothing looks like it shouldnt be there, I also looked in gpedit.msc and it is "Not Configured" so thats not the problem... so... yea maybe a full Install?

Nick - Before you go full reinstall - why not try an In Place Upgrade - where you boot from the DVD you used to install Win 7 and choose a non-destructive upgrade of the OS. It will reset Windows to it's default files and settings - and you're going to need to do an Activation again as well as setting things up (screen saver, background, etc..) but you won't have to reinstall your apps or back up your data. You might need to visit Windows Update again as well. Still a lot quicker than backing up, followed by a nuke and pave.

agreed, will try that this weekend when i have some time to play with. I will get back to you with the results! Cheers, Nick

Darien - Long time no see! Welcome back!That policy you mentioned is also available for the local group policy as well. Good to be back. I have been monitoring the forums; just did not have much to contribute.

Hey all, I have just Done a In Place Upgrade and then tried to run CMD and, it still doesnt work. Anyone think i should download another Buld

Cyberbeat, The only supported build available from Microsoft at the moment is the RC (Build 7100), unless you were thinking about reverting to the beta, which will expire soon.-Alex

Cyberbeat -Not really. If you download one of the "leaked" builds - you run the risk of downloading something nasty along with it. They've found these leaked builds have been spiked with preloaded malware. Unless you feel like turning your computer over to someone who wants to turn it into a member of his zombie army - then no.. probably not a good idea.You might as well try a back up, nuke and pave.

Does cmd.exe work if you double click it in explorer? It should be in C:\Windows\System32. Check the details. It should be version 6.1.7100.0, and copyright Microsoft.Does Start\Run\CMD work?Does Start\Run\C:\Windows\System32\cmd.exe work?What is the value of your %Path% environment variable. If any of the above tests work, type set p in the cmd window. Check the setting for Path in Control Panel\System>Advanced Settings>Environment. When you view it, it should start with C:\Windows\system32;C:\Windows. If you open it for editing,it should start with "%SystemRoot%\system32;%SystemRoot%;".You can also look in the Registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment, HKEY_CURRENT_USER\Environment, and also HKEY_CURRENT_USER\Volatile Environment. Normally only the first one or two will have a Path value.

Hey Bnborg, Typing CMD into run doesnt work, Nor does Typing the wholeC:\Windows\System32\cmd.exe When the path setting is: When it is opened for editing; %SystemRoot%\system32\cmd.exe i think i might as well go for a Nuke and Pave! I will do that when i got a couple of hours free (0r if schools close with H1N1). lol Cheers for the replies everyone i will get back to you with the results, Cheers Nick www.cyberbeatinternational.com

Hi! I have the same problem in Windows 7. Doubleclicking a .bat file starts up the cmd environment in background. I can se the processini task manager, but it doesn't show up on the screen and not in the task bar. Same problem if I type cmd in the "run" box. However if I create a shortcut to cmd.exe the cmd window shows up. If I type "command" in the "run" box the DOS command environment shows up. Sorry to say that those methods does not help me. I want the cmd window to show up when doubleclick the bat-file. /Tojak

Tojak: If you just want the window open so you can see any output, you could just put a pause or timeout /t [seconds] at the end. If you want to be able to use the window for entering additional commands, it will take a little more doing. If the bat file is opened with a shortcut, you can add the /K switch to the "Target" line, such as, "cmd /K [path\]target.bat". This would leave the cmd window open when the batch terminates. Otherwise you could try to change the command line for .bat files using "Default Programs", but I have no idea how to do that. My approach would be to edit the registry, but you do so at your own risk. The value under the key HKEY_CLASSES_ROOT\batfile\shell\open\command is "%1" %* which just means to pass windows the batch file, with any parameters. Changing it to "cmd.exe /k %1" %* should pass cmd.exe the /k switch and then the batch file name and path. Windows Command-Line-Reference.