Skip to main content
19 events
when toggle format what by license comment
Mar 26 at 9:45 audit First answers
Mar 26 at 9:47
Mar 20 at 22:07 audit First answers
Mar 20 at 22:07
Mar 7 at 11:21 history edited grawity_u1686 CC BY-SA 4.0
added 169 characters in body
Mar 5 at 18:44 comment added Joel Coehoorn The one issue I take with this is the comparison between vbscript vs powershell disabled status. Powershell is only enabled out of the box if you're talking about signed scripts, and it's unlikely the OP has gone that far. So, effectively, the vbscript and powershell situations are reversed: vbscript is enabled unless someone has taken affirmative action to disable it, and powershell is disabled unless you take affirmative action with your script to allow it.
Mar 5 at 13:27 comment added Voo One important - and easily forgotten - QOL thing is to call the PowerShell script with powershell.exe -file <blabla> -ExecutionPolicy Bypass -NoProfile. For larger rollouts or in enterprises it'd also be a good idea to sign the script (that way you can usually get around Lars' problems with execution - at least if the IT security is competent and works with you)
Mar 5 at 11:36 comment added Lars Kristensen @T.Sar Also a valid point that OP should definitely consider. However, OP is specifically asking about Windows in this question.
Mar 5 at 11:28 comment added T. Sar @LarsKristensen Having the scripting engine disabled by a reason or another can happen in linux, too. It's not an issue specific to Windows.
Mar 5 at 10:08 comment added Voo @Lars By the same logic: You can also block executables from running. Any environment that blocks scripts from running will almost certainly also whitelist their executables.
Mar 5 at 9:30 comment added Lars Kristensen @u1686_grawity I'm not sure what type of script it is, but the same question could be asked for .cmd or .bat files. My point is; an application (portable or installed) can be allowed to run, while scripts at the same time can be prevented from running. I would also reccommend OP to utilize PowerShell for this functionality, but to be aware that scripting of any kind can be disabled.
Mar 5 at 9:20 comment added grawity_u1686 @LarsKristensen: Isn't "Open in Notepad" the default action for .ps1 scripts, though?
Mar 5 at 9:19 comment added Lars Kristensen @u1686_grawity That is true, and my workplace is in a bank - However, I have a concrete example of exactly this issue, where IT has approved that Docker can be installed on developers machines, but an "Update Script" related to Docker is prevented from running, and instead opens in Notepad.
Mar 5 at 6:47 comment added grawity_u1686 @LarsKristensen: I can imagine that being done in banks or whatever, but I suppose if you get to that point, you're already in a situation where the IT team would Really Prefer if you asked for approval before running your portable apps from a USB stick either way...
Mar 5 at 6:34 comment added Lars Kristensen FWIW, PowerShell and other built in scripting languages in Windows can also be disabled in corporate environments (I'm facing this issue right now).
Mar 4 at 16:39 comment added grawity_u1686 Then you can write the updater as another Lua script turned into an .exe, no?
Mar 4 at 16:33 vote accept Reverent Lapwing
Mar 4 at 16:33 comment added Reverent Lapwing It does seem that PowerShell is the best option. I don't exactly ship a "compiled program" - it's a Lua script concatenated with a precompiled framework that together form the exe of the program. Writing a compiled helper program for such a simple task is a bit overkill if it can be avoided.
Mar 4 at 15:54 history edited grawity_u1686 CC BY-SA 4.0
deleted 6 characters in body
Mar 4 at 15:21 comment added phuclv you can use powershell or vbs to show a GUI and hide the console though
Mar 4 at 14:04 history answered grawity_u1686 CC BY-SA 4.0