Paths and directories not found for Windows Server on Google Cloud

[AndrewManHayChiu]

I expected to be able to open the Parsec application after running the script in the README, but parsec does not seem to be installed/moved.

I tried running the script, but encountered the following error messages after running the script in PowerShell:

Installing Parsec
Downloading and Installing 7Zip
Moving files to the correct location
Move-Item : Cannot find path 'C:\ParsecTemp\Apps\Parsec-Windows\$APPDATA\Parsec' because it does not exist.
At C:\Users\[username]\Desktop\parsectemp\PostInstall\PostInstall.ps1:442 char:73
+ ... e) {} Else {Move-Item -Path 'C:\ParsecTemp\Apps\Parsec-Windows\$APPDA ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (C:\ParsecTemp\A...$APPDATA\Parsec:String) [Move-Item], ItemNotFoundExce
   ption
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.MoveItemCommand

Installing ViGEmBus - https://github.com/ViGEm/ViGEmBus
Creating Parsec Firewall Rule
Creating Parsec Service
Successfully installed Parsec
Out-File : Could not find a part of the path 'C:\Users\amhchiu\AppData\Roaming\Parsec\config.txt'.
At C:\Users\[username]\Desktop\parsectemp\PostInstall\PostInstall.ps1:495 char:29
+ ... p_host=1" | Out-File -FilePath $ENV:AppData\Parsec\config.txt -Encodi ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (:) [Out-File], DirectoryNotFoundException
    + FullyQualifiedErrorId : FileOpenFailure,Microsoft.PowerShell.Commands.OutFileCommand

Start-Process : This command cannot be run due to the error: The system cannot find the file specified.
At C:\Users\[username]\Desktop\parsectemp\PostInstall\PostInstall.ps1:496 char:1
+ Start-Process -FilePath "$ENV:AppData\Parsec\electron\parsec.exe"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Start-Process], InvalidOperationException
    + FullyQualifiedErrorId : InvalidOperationException,Microsoft.PowerShell.Commands.StartProcessCommand

A Parsec shortcut is created on the Desktop, but it is not linked to an executable file, and so Parsec does not run.

Everything else seems to run smoothly.

This was replicated in both Windows Server 2016 and Windows Server 2019.

[jamesstringerparsec]

The Parsec application has changed and will no longer be visisble to RDP connections.

Ignore the errors and follow the rest of the script instructions (including installing GPU driver and setting up auto login), ignoring the part about logging into Parsec.

Reboot the machine, connect via VNC and you will now be able to see and login to Parsec.

RDP and Parsec are not compatible.

You can find Parsec in C:\Program Files\Parsec\parsecd.exe <- you can make a working desktop shortcut from that application.

A change to remove the error messages from the script and fix the icon in the next few days.

[AndrewManHayChiu]

Thanks for the information.

This solved my issue.

Thanks!

[jamesstringerparsec]

I'm going to leave this open because others will have this issue and this information will be helpful

[jamesstringerparsec]

This is resolved