Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Just delete the [scriptname].wsh file in the same directory as the script. Possibly that's been made read-only or similar? </p> <p>That's the file that contains the settings. You can find more details in this MSDN article: <a href="http://msdn.microsoft.com/en-us/library/h8fe3wt9%28VS.85%29.aspx" rel="nofollow">Setting and Customizing Script Properties (.wsh)</a></p> <p>Edit: Some new suggestions that might help:</p> <p>Try going to this key in the registry: <code>HKLM\Software\Microsoft\Windows Script Host\Settings</code> and checking if there is a setting in there that might be the reason. Might be worth going to the same path but under <code>Current User</code> as well (so <code>HKCU\Software\Microsoft\Windows Script Host\Settings</code>).</p> <p>Otherwise there is an option in the Group Policy Editor called <a href="http://technet.microsoft.com/en-us/library/cc938768.aspx" rel="nofollow">Maximum wait time for Group Policy scripts</a>. I don't think this would affect you but might be worth making sure.</p> <p>Finally, if neither of the above suggestions help maybe either of the following might at least alleviate the problem: There is a property called <code>WScript.Timeout</code> which you can set at the beginning of your scripts (like <code>WScript.Timeout = 60</code>) that might help. There is also a command line parameter <code>\T</code> to <code>wscript</code> that can be used to setting the timeout as described <a href="http://msdn.microsoft.com/en-us/library/xazzc41b%28VS.85%29.aspx" rel="nofollow">here</a>.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload