MScholtes

Hello @chrisloup, thank you for your feedback. Unfortunately, _Powershell_ only gives partial or misleading information about the _Windows_ version. Can you run **winver.exe** or "**cmd.exe /c ver**" on the three...

Hello @chrisloup, thank you for your feedback, but to use the example version manually, you have to dotsource the script: ```powershell . .\VirtualDesktop3085.ps1 ``` (the leading . is important) Greetings...

Hello, I updated this repository today and the package on PowerShell Gallery. With ```powershell Update-Module VirtualDesktop ``` or ```powershell Install-Module VirtualDesktop ``` you can install the new version 1.5.7. I...

Hello @kilasuit, please post the Windows version you are using (output of **WinVer.exe)**. Which version of the **Virtual Desktop** module you are using? Greetings Markus

Hello @kilasuit, it is sad to hear that the changes are not working for the _Canary Insider_ channel. Unfortunately, due to the effort involved, I can't provide support here -...

Hello @igorakkerman, Microsoft does not publish any documentation on the interfaces for virtual desktops, as it believes that these functions should only be set by the user. With every new...

Issue solved but of Canary versions, but no support for this version

Hello @NabiKAZ, calling **Virtualdesktop.exe** without parameter is detected as an error and returns **ERRORLEVEL** 2. If you want to show the help text please use **Virtualdesktop.exe /?**, **Virtualdesktop.exe /h** or...

Hello @NabiKAZ, I think I understand the issue now. But the real challenge here is that I intentionally set the last result as error level so that it can be...

Hello @NabiKAZ, there's an very old convention on Unix, CP/M, DOS, Z/OS etc. that an exit code or return code of 0 for command line tools means success, other values...