Windows 10: I can no longer run bat file as Admin (cmd flickers then closes)

I made a working script for my windows to mount and unmount drives and it works but it requires admin permission. right after i made the script i saved it and test it and it was working fine, i tested it about 15 times and it works.
then i reboot and the script no longer runs as admin anymore if i run int without admin it works but cant carry out the command due to lack of permission and if i try to run as admin the cmd window flickers for a split second and closes. the script is indeed correct and working because if run the bat through the task manager as admin that works just fine. how is this even possible?

:)

 

My Batch File(.bat) is no longer running CMD

My Batch File(.bat) is no longer running CMD and when i go and change the program and find CMD and or Command Prompt it says that the program that i chose cannot be associated with this file type. Please choose another. I ran CMD with .bat file before, but
now i can't. I there a solution to this, please?

Original Title: Set Associations

 

.bat files

it depends a little on what the batch file is doing, running from within windows it will open a cmd prompt run the commands and close the command prompt.

outputs from the commands (including errors) are lost when the batch file finishes and closes the command prompt.

if it is trying to run something that requires admin privileges, it will simply produce an error that is lost.

if you are running from a shortcut try cmd /k batchfile.bat
that should leave the command prompt open when the batchfile terminates

 

Hi xdarkmario

Have a read of this thread. Maybe, just maybe it will help.

bat job started by Task Scheduler does not pause


Ken

 

Try this: Create shortcut of the bat and set the shortcut to run as admin.

 

it took me all day to learn how to wright that batch file yet alone learn how to learn powerscript, thats a whole other level

Already tried that and it does not work

 

Are your tests before & after reboot using the exact same conditions? - e.g. both being initiated using a shortcut / both being initiated by Task scheduler / both being initiated by a command entered in an elevated command prompt / both being run by the same user account & the same authorising Admin account

Denis

 

found the issue, it dosent seem to like "&" in the file name. After removing the "&" the script works again.