System will not run .bat files

Page 2 of 2 FirstFirst 12

  1. Posts : 5,656
    Windows 7 Ultimate x64 SP1
       #11

    Ok, why not just copy paste it from the winsxs folder to System32? Or even winsxs is deleted too?

    I just copy pasted to desktop and it worked double clicking too (opened as C:\Users\Gokhan\Desktop).

    Edit: In case permissions stop you from browsing there, try GiveMePower Download
      My Computer


  2. Posts : 10,485
    W7 Pro SP1 64bit
       #12

    GokAy said:
    Ok, why not just copy paste it from the winsxs folder to System32? Or even winsxs is deleted too?

    I just copy pasted to desktop and it worked double clicking too (opened as C:\Users\Gokhan\Desktop).

    Edit: In case permissions stop you from browsing there, try GiveMePower Download
    If you were able to copy the real cdm.exe file from the protected winsxs area and paste a copy into the System32 folder, then SFC scans would probably indicate an error. I am guessing that a cmd.exe file in the System32 folder is easier to infect. Hard Links seem to be a part of Windows security scheme. See the link inside the quote in my last post.

    Our goal should be to return the OP's computer to a state as close to what Microsoft designed as possible. Not just make it functional. For example: turning off the UAC leaves a computer functional :-(
      My Computer


  3. Posts : 5,656
    Windows 7 Ultimate x64 SP1
       #13

    Yes, I understand what you are saying.

    Use the cmd in winsxs to create the hardlink and try? I am about to go out for my daily walk, so won't be able to test in a VM until 2 more hours.

    But perhaps sfc would work from the winsxs? Another thing to check in VM :)
      My Computer


  4. Posts : 10,485
    W7 Pro SP1 64bit
       #14

    GokAy said:
    ~~~
    But perhaps sfc would work from the winsxs? Another thing to check in VM :)
    It does work (in my VM). See below. It reports an issue that it cannot fix with the cmd.exe file, but a reboot and another SFC shows no integrity violations. I'm just not willing to suggest it without more opinions/testing. If you get the same results, then I guess we can recommend it to the OP.

    From post #10:
    [QUOTE=UsernameIssues;3115259]
    GokAy said:
    ~~~
    The long path that I show in the cmd screenshot is the actual 64bit cmd.exe file. It will run SFC on a 64bit system and that will fix the hard link that was deleted. I'm just not sure if SFC is the best way to handle this. Maybe others can chime in.
      My Computer


  5. Posts : 5,656
    Windows 7 Ultimate x64 SP1
       #15

    I am starting to test in a VM, will edit this post as I go.

    Edit 1: Deleted cmd.exe inside System32 and cmd fails to open "Windows cannot find 'cmd'...."

    Edit 2: Sorry it took a while, had trouble either with the mklink command or a permission. The same command worked finally! :) Double click from System32 works, cmd at run box works. Now, running sfc /scannow
    Last edited by GokAy; 25 Jul 2015 at 09:41.
      My Computer


  6. Posts : 5,656
    Windows 7 Ultimate x64 SP1
       #16

    Ok, sfc /scannow finished with no violations.

    System will not run .bat files-cmd.exe-deleted-sfc-scannow-result.jpg
      My Computer


  7. Posts : 10,485
    W7 Pro SP1 64bit
       #17

    Thanks for testing.

    Maybe these steps will work for the OP:
    1) run SFC from winsxs
    2) reboot
    3) run SFC from winsxs

    Here is the info to run SFC:
    click Start
    paste this in the search area
    Code:
    c:\Windows\winsxs\amd64_microsoft-windows-commandprompt_31bf3856ad364e35_6.1.7601.17514_none_e932cc2c30fc13b0\cmd.exe
    right click on cmd.exe
    run as admin
    type in sfc/scannow
    (no space needed after sfc)
      My Computer


  8. Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       #18

    Not knowing for sure everything that has been changed or deleted I would suggest doing a Repair install.

    A tutorial by Brink:

    Repair Install
      My Computer


  9. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #19


    As Jack suggests, this could well just be the tip of a large iceberg, and a repair is probably the best option in the longer term.
      My Computer


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:53.
Find Us