WindowWidth Issue

[FlyingDodo86]

When starting the script i get the following message (used Power ISE to check). Any idea what is going wrong?

"
In Zeile:92 Zeichen:1

• [console]::WindowWidth=77; #script has been designed around this widt ...

•   + CategoryInfo          : NotSpecified: (:) [], SetValueInvocationException
    + FullyQualifiedErrorId : ExceptionWhenSetting
  

[shupershuff]

This issue hasn't been brought up before, are you running from within powershell ISE?
What happens if you launch it normally from windows explorer?

[FlyingDodo86]

When executing via Powershell it just closes but the exe File is not generated.

If you're interested to look into the issue and require more Informationen, happy to support.

[shupershuff]

What operating system are you running?
Also what version of powershell is in use?
Use $PSVersionTable.PSVersion to find out.

[FlyingDodo86]

I just did a cleaninstall of windows 11 but still the same.

PowerShell Version:
Major Minor Build Revision
5 1 26100 2161

[FlyingDodo86]

FYI, I've tried it with version [v1.13.2] and there it works without any issues. Even the prompt to update to the latest caused no issues.

[shupershuff]

The command is the same in 1.13.2. What did change was the window height part, but that comes after where it says you got the error message.
What happens when you type this into PowerShell: [console]::WindowWidth=77

Also had you edited the script in anyway?

[shupershuff]

When running it, are you right clicking it in explorer and choosing 'run with PowerShell'.
Also what happens if you change 77 to say 150 and run it?

[FlyingDodo86]

I cant reproduce the issue. Downloaded latest again and this time no Problem at all. Have no clue why as I havent done anything differently. I also did not modify anything previously. I Only can imagine that it could be related to deleting the settings.json as I was following the switch config instructions with the installation and setup with the previous Version. Works like a charm. Many thanks for your efforts.

[shupershuff]

Yea it's an odd one. Good to know it's working now :)
Shout out if you see the issue happening again and we can investigate further.