The problem has been identified. RSL has implemented hidden new anti-virus rules a week prior to my new build.
This wasn't mentioned in any release ofc, nor was it properly tested in advance ... .
Thank you for your time and effort.
Search found 42 matches
- Mon Oct 02, 2023 5:11 am
- Forum: Former and Future Customers - Questions
- Topic: Unable to open newly build executable (EXE) -> Windows cannot access the specified device, path, or file.
- Replies: 15
- Views: 20561
- Sun Sep 03, 2023 11:45 pm
- Forum: Former and Future Customers - Questions
- Topic: Unable to open newly build executable (EXE) -> Windows cannot access the specified device, path, or file.
- Replies: 15
- Views: 20561
Re: Unable to open newly build executable (EXE) -> Windows cannot access the specified device, path, or file.
Ok thanks for clarifying. I've uploaded the build file.
- Thu Aug 31, 2023 2:14 am
- Forum: Former and Future Customers - Questions
- Topic: Unable to open newly build executable (EXE) -> Windows cannot access the specified device, path, or file.
- Replies: 15
- Views: 20561
Re: Unable to open newly build executable (EXE) -> Windows cannot access the specified device, path, or file.
As for uploading, it contains some sens info so i'd rather not straight away. The only thing that changed was : $RegexSam = "^[0-9]{7}$|^[0-9]{7}adm$" became $RegexSam = "^[0-9]{7}$|^[0-9]{7}(adm|admin)$" But i'd be surprised this has anything to do with it ? As for the screensho...
- Wed Aug 30, 2023 11:48 pm
- Forum: Former and Future Customers - Questions
- Topic: Unable to open newly build executable (EXE) -> Windows cannot access the specified device, path, or file.
- Replies: 15
- Views: 20561
Re: Unable to open newly build executable (EXE) -> Windows cannot access the specified device, path, or file.
The data that gets removed are:
- File version
- Product Name
- Product Version
- Copyright
- Language
- File version
- Product Name
- Product Version
- Copyright
- Language
- Wed Aug 30, 2023 8:25 am
- Forum: Former and Future Customers - Questions
- Topic: Unable to open newly build executable (EXE) -> Windows cannot access the specified device, path, or file.
- Replies: 15
- Views: 20561
Re: Unable to open newly build executable (EXE) -> Windows cannot access the specified device, path, or file.
Yeah i figures as much, i did a test on the local drive but that didn't resolve it either. I will test again tomorrow and get back to you. Thanks for the response and help. if that doesn't help, i might try to install PStudio on a different device and try to build from there. I don't see much other ...
- Wed Aug 30, 2023 7:58 am
- Forum: Former and Future Customers - Questions
- Topic: Unable to open newly build executable (EXE) -> Windows cannot access the specified device, path, or file.
- Replies: 15
- Views: 20561
Re: Unable to open newly build executable (EXE) -> Windows cannot access the specified device, path, or file.
SAPIEN Package and Deploy Tool 4.2 (c) 2005 - 2020 SAPIEN Technologies, Inc. ------ Build started: SD-Assistant, Configuration: x64 ------ Packaging with SAPIEN PowerShell V5 Host (Windows Forms) x64 Adding C:\Users\zztemp\OneDrive - CM-MC\Desktop\PROJECTS\SD-Assistant\SD-Assistant.Package.ps1 Writi...
- Wed Aug 30, 2023 7:23 am
- Forum: Former and Future Customers - Questions
- Topic: Unable to open newly build executable (EXE) -> Windows cannot access the specified device, path, or file.
- Replies: 15
- Views: 20561
Re: Unable to open newly build executable (EXE) -> Windows cannot access the specified device, path, or file.
Are you attempting to run the build directly from the file, not a shortcut? --> Yes, directly from de build file not a shortcut Try checking to see if your antivirus software is blocking the file and verifying the permissions of the file. --> Antivir isn't the issue. I have permissions on the file (...
- Wed Aug 30, 2023 6:00 am
- Forum: Former and Future Customers - Questions
- Topic: Unable to open newly build executable (EXE) -> Windows cannot access the specified device, path, or file.
- Replies: 15
- Views: 20561
Unable to open newly build executable (EXE) -> Windows cannot access the specified device, path, or file.
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: Product: PowerShel...
- Mon Mar 08, 2021 4:08 am
- Forum: PowerShell GUIs
- Topic: Managing Fonts for all controls by code
- Replies: 5
- Views: 4132
Re: Managing Fonts for all controls by code
Hi,
My PowerShell is decent enough but i got lost in all the examples in C# on the net.
I over complicated things. Thank you very much for your help jvierra.
My PowerShell is decent enough but i got lost in all the examples in C# on the net.
I over complicated things. Thank you very much for your help jvierra.
- Mon Mar 08, 2021 1:46 am
- Forum: PowerShell GUIs
- Topic: Managing Fonts for all controls by code
- Replies: 5
- Views: 4132
Re: Managing Fonts for all controls by code
Hi, thanks for your feedback. With that i've come to the following piece of code: foreach ($control in $form1.Controls) { $properties = [System.ComponentModel.TypeDescriptor]::GetProperties($control) foreach ($property in $properties.GetEnumerator()) { $property.Font = New-Object System.Drawing.Font...