Search found 8 matches
- Mon Nov 22, 2021 3:00 am
- Forum: PowerShell Studio
- Topic: ScriptContainedMaliciousContent
- Replies: 4
- Views: 4172
Re: ScriptContainedMaliciousContent
Found the issue. It always thrown, if you use something like: Start-Process $path You now must alway use a static path without variables to get the .run.ps1 File running. Right now it is impossible to get the created exe-File running: Screenshot 2021-11-22 120049.png Its not very fun to use ps studi...
- Mon Nov 22, 2021 1:31 am
- Forum: PowerShell Studio
- Topic: ScriptContainedMaliciousContent
- Replies: 4
- Views: 4172
Re: ScriptContainedMaliciousContent
You got me wrong. My exe-Files i created with PS Studio are blocked on any current windows. Even on my local development machine the .run.ps1 Files are blocked, which worked for 8 years. You may have recognized any changes in the last windows updates regarding your packager and could give me a hint,...
- Thu Nov 11, 2021 8:17 am
- Forum: PowerShell Studio
- Topic: ScriptContainedMaliciousContent
- Replies: 4
- Views: 4172
ScriptContainedMaliciousContent
Hi, years old and productive gui-projects are blocked by windows defender since today with following error. My suspicion is that the embedded icons for a warning. ERROR: Das Skript enthält schädliche Daten und wurde von Ihrer Antivirensoftware blockiert. ERROR: + CategoryInfo : ParserError: (:) [], ...
- Fri Apr 12, 2019 3:05 am
- Forum: PowerShell Studio
- Topic: Packager of 5.6.161.0 is definetly broken!!!!
- Replies: 9
- Views: 3832
Re: Packager of 5.6.161.0 is definetly broken!!!!
But one other thing remains: All unicode-signs like ä,ö,ü, ß are wrong in the gui after packaging
- Fri Apr 12, 2019 2:54 am
- Forum: PowerShell Studio
- Topic: Packager of 5.6.161.0 is definetly broken!!!!
- Replies: 9
- Views: 3832
Re: Packager of 5.6.161.0 is definetly broken!!!!
Ok, this works. Found one other problems with different paranthesis handling in this version (i could fix this by myself). I am wondering, because this part of the programm is more than four years old and did work all time along. And it does in the studio version 5.6.160.0. All scripts are encoded i...
- Thu Apr 11, 2019 9:06 am
- Forum: PowerShell Studio
- Topic: Packager of 5.6.161.0 is definetly broken!!!!
- Replies: 9
- Views: 3832
Re: Packager of 5.6.161.0 is definetly broken!!!!
Which script? All my files are created inside powershell studio. I never saw the option to change the encoding of scripts-files in studio. And no i don't use "Resolve and include external scripts". I mark them as shared.
- Thu Apr 11, 2019 7:44 am
- Forum: PowerShell Studio
- Topic: Packager of 5.6.161.0 is definetly broken!!!!
- Replies: 9
- Views: 3832
Re: Packager of 5.6.161.0 is definetly broken!!!!
If i pack it to consoleapplication, it doesnt bootstrap. As window app it shows: Line 11972: In Zeile:11971 Zeichen:60 + ... $value = $CommandLine.Substring($index + 1, $closeIndex – ($i ... + ~ ")" fehlt in einem Methodenaufruf. In Zeile:11971 Zeichen:61 + ... ue = $CommandLine.Substrin...
- Thu Apr 11, 2019 7:21 am
- Forum: PowerShell Studio
- Topic: Packager of 5.6.161.0 is definetly broken!!!!
- Replies: 9
- Views: 3832
Packager of 5.6.161.0 is definetly broken!!!!
To help you better we need some information from you. *** Please fill in the fields below. If you leave fields empty or specify 'latest' rather than the actual version your answer will be delayed as we will be forced to ask you for this information. *** Product, version and build: 5.6.161.0 32 or 64...