I got a win 8.1 machine that I have setup a local startup policy under gpedit.msc

Windows settings

scripts

startup

there is a install.bat file there that calls and executable in c:\scripts

The file is not executing on startup. 

any idea?

When I run the install.bat manually it runs fine

See if the following thread helps:

https://social.technet.microsoft.com/Forums/en-US/795b4141-2053-49d2-bd50-7213432bc224/startup-script-will-not-run?forum=ITCG

my machine is not using domain gpo. ITs a local gpo from gpedit. All it does is checks and installs antivirus

but the startup script it not running. after i login, I can run it manually and it works fine. the machine is not in a domain. Its it standalone in a workgroup

any idea on this? Its local policy and cannot run a simple bat file

Can I get some help here? This is all windows 8.1 and not domain related. why isnt a simple startup script not executing when windows 8.1 reboot?

what's the nature of the batch file?
is it doing any logging? (do you know if the batch file is executing at all)

maybe the batch file *is* executing but the commands within it are failing silently?

is the batch file trying to access any kind of network location? (does it have permissions)

any event logs from GP processing?

Hi JonDoe321,

To test whether this issue is related to the specific script, we can try to configure another script to have a troubleshoot.

"All it does is checks and installs antivirus"
Considering you are configuring the startup script to install antivirus, I am afraid it is not available to perform an installlation during logon process.

Best regards

Hi JonDoe321,

To test whether this issue is related to the specific script, we can try to configure another script to have a troubleshoot.

"All it does is checks and installs antivirus"
Considering you are configuring the startup script to install antivirus, I am afraid it is not available to perform an installlation during startup process.

Best r

in a domain gpo startup script, what user does the script run as?

in a domain gpo startup script, what user does the script run as?

computername$

(i.e. the domain computer account aka LocalSystem)

Startup scripts begin executing before any user has logged on, so they must run in the context of a builtin security principal. non-domain-members or Local GP startup scripts will run as LocalSystem. In a domain-joined scenario, LocalSystem is equivalent to the computer account.

If your script is needing to access network resources (e.g. a file share or a website), those network resources must grant access to computername$, or, Domain Computers, or, Authenticated Users, or some equivalent security group which represents domain-member-computers.

If your script is failing, some logging within the script might help you identify where and why it's failing. (e.g. insufficient permissions)

Does your power shell script has space in file name? If so try removing/replacing the space in file name and try again.