Hi @roland,
There are some workarounds that you can try, please check the Troubleshooting -> Network Connection -> VPN (Virtual Private Network) chapter in the user manual https://forum.spacedesk.netuser-manual/#item_493.
If it did not help, then there’s nothing else we can do but to disable your VPN for spacedesk discovery to work.
Hallo,
seit ich den VPN Access Manager installiert habe, funktioniert Spacedesk nicht mehr:
“Primäre Maschine kann nicht erkannt werden”
Gibt es eine Lösung.
Roland
Hi @leungzw,
spacedesk automatically configures the Windows Firewall to allow spacedeskService during installation, you can verify it via Control Panel\System and Security\Windows Defender Firewall\Allowed apps.
Maybe you can also try to manually create an Inbound/Outbound rules in the Firewall settings for spacedeskService.
spacedesk uses TCP port 28252.
By the way, what is the current network profile on your primary machine? Public or Private?
Are both WiFi network on primary machine and cellphone have the same network band/frequency (e.g. 2.4GHz or 5Ghz)?
Network isolation is not activated on Router1.
I can ping my pc 192.168.2.229 on my cellphone correctly.
which port spacedesk use to transfer data? Is it related to firewall settings?
Hi @leungzw,
For further analysis, could you please open the spacedesk Driver Console -> Diagnostics, then click Save All Information button.
PS: Saving all information will take a few seconds, then please send us the whole folder which contains all the diagnostic logs collected.
Please right-click the folder -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.
Hi @jamesson,
Did you also calibrate the SonarPen? And allow the Microphone permission in the SonarPen settings?
If yes and it still did not work, please send us the diagnostic logs of this issue for further analysis.
– open spacedesk Driver Console -> Diagnostics in your primary machine
– if Debug View is not available, please click the download button first
– switch Diagnostic Collection ON
– try to connect your viewer app and reproduce the issue (by sending several SonarPen input from your Android viewer)
– switch Diagnostic Collection OFF
– click Save All Information button
PS: Saving all information will take a few seconds, then please send us the whole folder which contains all the diagnostic logs collected.
Please right-click the folder -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.
Hi @monky,
Could you please try the following on your primary machine.
– right-click C:\Windows\Temp folder -> Properties -> Security tab -> Advanced -> Permission tab -> Continue
– check if you find the Users or Authenticated Users and make sure it has Full Control access
If none, just Add -> Select a principal, then type “Users” and click Check Names and click OK
– Then make sure to check the Full Control access for the Users then click Apply -> OK.
After following the steps above try to run-install again the spacedesk MSI installer.
Hi @wulf,
Thank you very much for sending the requested logs.
For the spacedesk Console app issue, we will release a potential fix for this issue in the next version.
For the display off issue, could you please download the spacedesk diagnostic script here, then extract it.
https://www.dropbox.com/s/okjvl3v4g8xmknq/2022_spacedeskDiagnosticTool.zip?dl=0
The folder contains spacedeskDiagnosticTool.cmd, just right-click it, then run as administrator.
On step 5 it will prompt you to reproduce the issue (by connecting the viewer app and wait for the issue to happen), make sure to do this before pressing any key to continue.
After the script is done, a folder will be created in the same folder as the script file which contains various log files that we need for analysis.
Please right-click it -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.
Hi @jamesson,
Did you enable the SonarPen in the spacedesk Android Viewer settings -> Input Devices -> Pen -> SonarPen Stylus?
Please check the attached screenshot for assistance.
Alright, I tried to install .NET Framework and it said I already had it installed. Spacedesk is still not working.
Hi @angels11_6,
You can easily setup the layout of your video wall by setting the correct Position (X;Y) of each clients, in the Video wall settings tab (of spacedesk Driver Console).
For assistance, please check the Video Wall Configuration chapter in the user manual https://forum.spacedesk.netuser-manual/.
Hi @wulf,
Could you please send us the current .NET Framework version of your primary machine.
Just run the Windows PowerShell as Administrator then type the command:
Get-ChildItem ‘HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP’ -Recurse | Get-ItemProperty -Name version -EA 0 | Where { $_.PSChildName -Match ‘^(?!S)\p{L}’} | Select PSChildName, version
Then press the Enter send us the result via txt file or screenshot.
Please check this link for reference: https://www.windowscentral.com/how-quickly-check-net-framework-version-windows-10
Could you also please send us the following for further analysis:
– Dxdiag.txt file – just run dxdiag.exe on your primary machine, click “Save All Information”
– C:\Users\Public\spacedeskSetup.log file
Please save all requested files in one folder, then right-click -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.
For assistance, you can also check the Troubleshooting -> Windows PC (Primary Machine) chapter in the user manual https://forum.spacedesk.netuser-manual/.
Hi @pen1350,
Is it a flickering screen when you said “PC crashed for around 10 seconds”?
Can it still recover after disconnecting the spacedesk viewer?
Can you quickly check in spacedesk Driver Console -> Diagnostics -> Incompatible Software, if Nvidia ShadowPlay/In-game Overlay/screen recording is active?
If it’s active, please stop/disable your Nvidia ShadowPlay then try again with spacedesk.
If it did not help, could you please send us the diagnostic logs of the issue.
– open the spacedesk Driver Console -> Diagnostics
– if Debug View is not available, please click the download button first
– switch Diagnostic Collection ON
– try to connect your viewer app and reproduce the issue (then disconnect immediately)
– switch Diagnostic Collection OFF
– click Save All Information button
PS: Saving all information will take a few seconds, then please send us the whole folder which contains all the diagnostic logs collected.
Please right-click the folder -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.
Hi @armada45
Thank you very much for sending the diagnostic logs.
Based on the logs, you have splashtop display hook driver (lci_proxywddm) running on your machine. This product is currently not compatible with spacedesk.
You have to uninstall it, then reboot before you connect a spacedesk viewer.
To uninstall, just open the splahstop Wired XDisplay Agent on your machine the click on Advanced, then Uninstall the Virtual display driver.
OR just open the spacedesk Drive Console -> Diagnostics -> Incompatible Software, then click the Uninstall button beside the lci_proxywddm driver, then reboot your primary machine.
Hi,
I cannot figure out the display settings (in the video wall console) for my video wall. Please see attached video wall diagram with measurements etc.
Can you please help with the exact display settings I need to be putting into the spacedesk video wall console to effect a seamless display.
I want to display 1 image spread over the three monitors.
Thanks in advance!
Angels
I just installed Spacedesk for the first time and my Android I am using as a second screen managed to detect the server and connect, however it displays “Connected – Display OFF” and a black screen. I am also unable to open the Spacedesk driver Console, it appears in the task manager for a few seconds before it disappears, with no popup or anything like that at all.
I tried spacedesk with my Android Phone today, but I´m having an issue in which that happens when I´m playing games om my main screen. When I alt+tab to see another thing while the game is open, my PC crashes for around 10 seconds, becomes all black, my phone disconnects and then my PC continues.
Also, this only happened once, but there was a time that my PC completly froze and started beeping when I alt+tab’ed and required an hard reboot
Specs:
-NVidia GTX 1660 Super
-I have a three monitor setup
Hi @janichols,
Can you please download the Microsoft Troubleshooter program here:
https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d
Run the “MicrosoftProgram_Install_and_Uninstall.meta.diagcab”, select Uninstalling.
If “spacedesk Windows DRIVER” is not on the program list, just select “Not Listed” then paste the product code of spacedesk_driver_Win_10_64_v0987_BETA.msi here: {CE7DC976-85B4-45B2-BDEB-A2C7B5BCA18F}
After that, please reboot your primary machine then try again to install the latest spacedesk msi installer from the website.
By the way, do you have third party antivirus software currently active on your primary machine?
Apple pressure sensitive pen support is not yet available.
Currently spacedesk iOS Viewer only supports Sonar Pen https://www.sonarpen.com/
Full pen support is currently only implemented on Android.
Android is the only spacedesk Viewer supporting the whole spacedesk feature set.
Eventually all features available on Android will also be ported to iOS on Apple devices.
This includes Apple pen. However, no official timeline yet.
We assume that you are talking about spacedesk Viewer for Windows.
We are aware of the described (Ultra)VNC approach.
We will implement this feature as soon as a corporate customer will pay for it.
This is not expected to happen any time soon.
In the meantime you could use the “Mouse as Touch” setting.
This uses the local mouse to raise touch events.
It is actually very close to the feature which you are requesting.
Please let us know how this works for you.
Hi @elfik,
Thank you for sending the video, and for verifying that you are using a virtual machine as primary machine.
spacedesk do not officially support virtual machines. You can install it there, but we cannot guarantee that it will work properly.
This is a known behavior of mouse pointer in virtual machines when there’s a second display connected.
We are actually not sure if this is a spacedesk issue or a limitation in virtual machines.
Hi @spetsnaz,
Please check in the spacedesk Driver Console, click on Incompatible Software to see if any are installed in your server device. If there are, you need to uninstall them for Spacedesk to properly work in your device. If there are no incompatible software installed in your server device, please send us the diagnostic logs for this issue in order for us to analyze the cause of the problem.
– open the spacedesk Console window app by clicking the spacedesk tray icon on your task bar’s notification area
– click the Diagnostics on the left side panel
– if Debug View is not available, please click the download button first
– switch Diagnostic Collection ON
– connect to server and wait for disconnection
– switch Diagnostic Collection OFF
– click Save All Information button
Saving all information will take a few seconds, then please send us the whole folder which contains all the diagnostic logs collected.
Please right-click the folder -> Send to -> Compressed (zipped) folder, then attach the *.zip file on your next reply. Thank you.
I have a suggestion for spacedesk, in that the mouse pointer can be rather slow on suboptimal networks. (Ultra)VNC has resolved this by showing the mouse target position instead of showing the transferred mouse pointer alone.
Could this be considered for this very useful software please?
Thanks,
Robbert
Thank you very much for sending the log file. We are currently analyzing it. Can you please also send us the updated C:\Users\Public\spacedeskSetup.log and C:\Windows\INF\setupapi.dev.log too?
Hi @kokko,
Routers can cause lags and latency. Bypassing them always improves performance.
Configure Windows 11 PC or iOS device as WiFi Access Point (Hotspot) and connect to it before connecting spacedesk.
USB Tethering achieves the same result.
Please check the chapter “Performance Tuning” in the instruction manual: https://spacedesk.net/user-manual
Hi @lrbsb,
For further analysis, could you please send us the diagnostic logs for this issue?
– open the spacedesk Driver Console app on your primary machine, then click the Diagnostics
– if Debug View is not available, please click the download button first
– switch Diagnostic Collection ON
– try to connect your viewer app and reproduce the issue
– switch Diagnostic Collection OFF
– click Save All Information button
PS: Saving all information will take a few seconds, then please send us the whole folder which contains all the diagnostic logs collected.
Please right-click the folder -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.
Hi @azzy,
Could you please quickly check if there’s any incompatible software present on your primary machine. Just open the spacedesk Driver Console -> Diagnostics -> Incompatible software.
For assistance, please refer to Troubleshooting -> Windows PC (Primary Machine) chapter in the user manual
https://forum.spacedesk.netuser-manual/.
Please rename the msi file name from “spacedesk_driver_Win_10_64_v1037_BETA (1).msi” to “spacedesk_driver_Win_10_64_v1037_BETA.msi”, then try again with the script.
Thanks for the suggestion. I tried this but unfortunately when the pc boots it connects to the spacedesk monitor but still only as extended monitor and not the primary. Any other suggestion would be appreciated.
-
該回覆由 oberon23 於 2 years, 7 months ago 修改。
I downloaded spacedesk_driver_Win_10_64_v1037_BETA (1).msi and put it in the folder, ran the BAT and it produced the following:
spacedeskmsi_trace.txt
=== Verbose logging started: 3/8/2022 9:20:22 Build type: SHIP UNICODE 5.00.10011.00 Calling process: C:\windows\system32\msiexec.exe ===
MSI (c) (E8:FC) [09:20:22:717]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (E8:FC) [09:20:22:717]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (E8:BC) [09:20:22:752]: Resetting cached policy values
MSI (c) (E8:BC) [09:20:22:752]: Machine policy value ‘Debug’ is 0
MSI (c) (E8:BC) [09:20:22:752]: ******* RunEngine:
******* Product: C:\Users\janic\Downloads\msi_trace\msi_trace\\spacedesk_driver_Win_10_64_v1037_BETA.msi
******* Action:
******* CommandLine: **********
MSI (c) (E8:BC) [09:20:22:755]: Note: 1: 2203 2: C:\Users\janic\Downloads\msi_trace\msi_trace\\spacedesk_driver_Win_10_64_v1037_BETA.msi 3: -2147287038
MSI (c) (E8:BC) [09:20:22:757]: MainEngineThread is returning 2
=== Verbose logging stopped: 3/8/2022 9:20:22 ===
Thank you very much for sending the logs. We are currently analyzing it.
For further analysis, could you please download and extract the zip file here: https://www.dropbox.com/s/rqayx759wdwmye2/msi_trace.zip?dl=0
Inside the folder, please copy the most recent spacedesk MSI installer (v1.0.37) then run the get_trace.bat script file.
The script will execute the msi installer (to reproduce the installation error) and will automatically generate a spacedeskmsi_trace.txt file, then please send the file to us after executing the failed msi installer.
There was no msi installer in the folder, only the BAT file to run the script.
Hi @panxinxin,
Can you tell us which spacedesk version did you install/uninstall?
Is your primary machine monitor still displaying properly after spacedesk uninstall and before restarting it?
Can you try to boot your machine in safe mode?
For assistance, please refer to this link https://www.drivereasy.com/knowledge/how-to-enter-safe-mode-in-windows-10/#why
Hi @janichols,
Thank you very much for sending the logs. We are currently analyzing it.
For further analysis, could you please download and extract the zip file here: https://www.dropbox.com/s/rqayx759wdwmye2/msi_trace.zip?dl=0
Inside the folder, please copy the most recent spacedesk MSI installer (v1.0.37) then run the get_trace.bat script file.
The script will execute the msi installer (to reproduce the installation error) and will automatically generate a spacedeskmsi_trace.txt file, then please send the file to us after executing the failed msi installer.
Thank you very much for sending the logs.
Based on the logs, you are trying to install an old spacedesk Driver version 0987.
Could you please try with the most recent spacedesk Driver (v1037) which is available on the website https://forum.spacedesk.net#download.
I would install the most recent driver but as the title says, I cannot update the current driver. I get an error message which then rolls back the driver to the previous one. I’m not TRYING to install the old driver.
Hi @oberon23,
It seems to remember the last desktop mode (extension) even after you detach your primary monitor.
Could you please try the following workaround:
– attach your primary monitor
– connect the spacedesk viewer
– switch to projector mode / second screen only via display switch (Windows logo key + P)
– detach your primary monitor
Try to restart your primary machine this time without your primary monitor attached and just try to connect your spacedesk viewer.
Hi @mikhal980,
Thank you very much for sending the requested logs.
Based on the logs, there’s a RPC_S_CALL_FAILED error (The remote procedure call failed) during spacedesk USB driver installation.
One of the causes of this issue:
– failed installation/uninstallation of software that may have left invalid entries in your system
– improper system shutdown due to power failure
Could you please try the following suggestions below:
1. Run services.msc then find Remote Procedure Call (RPC), and check if it’s running.
2. Make sure to install any pending Windows Update on your Windows Settings.
3. Your AMD graphics driver is not digitally signed, please try to repair/reinstall your AMD graphics driver. Just download the AMD Auto-detect tool here: https://www.amd.com/en/support, to update your AMD graphics driver properly.
4. Run Command Prompt as Administrator, then type the command: “sfc /scannow” and press Enter.
Hi @nekona,
Thank you very much for sending the requested logs.
Based on the logs, your primary machine – Surface Pro X is an ARM-based tablet which spacedesk driver do not support.
Hi @apollo163,
Is this only happening on spacedesk screen? Or also in your main monitor?
Could you please send us the diagnostic logs for this issue?
– open the spacedesk Driver Console -> Diagnostics in your primary machine
– if Debug View is not available, please click the download button first
– switch Diagnostic Collection ON
– try to connect your viewer app and reproduce the issue
– switch Diagnostic Collection OFF
– click Save All Information button
PS: Saving all information will take a few seconds, then please send us the whole folder which contains all the diagnostic logs collected.
Please right-click the folder -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.
Hi @itzzkaz,
Could you please check if there’s any incompatible software currently active on your Windows 11 machine?
Just run spacedesk Driver Console -> Diagnostics -> Incompatible Software.
If there’s none, could you please send us the diagnostic logs for further analysis, just follow the steps below:
– click spacedesk Driver Console -> Diagnostics
– if Debug View is not available, please click the download button first
– switch Diagnostic Collection ON
– try to connect your viewer app and reproduce the issue
– switch Diagnostic Collection OFF
– click Save All Information button
PS: Saving all information will take a few seconds, then please send us the whole folder which contains all the diagnostic logs collected.
Please right-click the folder -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.
Hi @romans,
You can easily do this by switching to Desktop Duplication (mirror) mode via Display Settings so you can remotely access your main monitor screen.
For assistance, please check Configuration and Settings -> Windows PC (Primary Machine) chapter in the user manual https://forum.spacedesk.netuser-manual/#item_469.
Hi @romans,
You can use your Spacedesk Viewer device as a remote desktop by duplicating your primary PC’s screen on the Viewer screen. For instructions on how to do this, please check our User Manual under the section “Configuration and Settings” -> “Desktop Extension or Desktop Duplication (mirror) Settings in Display Control Panel” by clicking the link below:
https://forum.spacedesk.netuser-manual/#item_470
Thank you!
Hi @nekona,
For further analysis, could you please send us the following:
– run dxdiag.exe on your primary machine, click “Save all information” and send us the output file
– spacedeskSetup.log file located in C:\Users\Public
– setupapi.dev.log file located in C:\Windows\INF
Please save all requested files in one folder, then right-click -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.
Hi @tymops,
Did you try to manually enter the IP address?
Do you have third party firewall software on your primary machine? Or maybe VPN (Virtual Private Network) currently active?
For assistance, please also check Troubleshooting -> Network Connection chapter in the user manual.
https://forum.spacedesk.netuser-manual/
Hi @superrumi,
Do you have third party firewall software on your primary machine? Or maybe VPN (Virtual Private Network) currently active?
For assistance, please also check Troubleshooting -> Network Connection chapter in the user manual.
https://forum.spacedesk.netuser-manual/
Hi @gennady46,
Have you tried dragging the window to the second monitor to see if it gets displayed there? If the window is displayed in the Primary PC’s monitor, you should be able to drag the window to the Viewer’s monitor for you to display it there. You can check the arrangement of the monitors by right-clicking on your desktop and clicking Display Settings on the menu that appears so you would know where to drag your windows to.
Alternatively, if you would like to duplicate the Primary PC’s monitor on your Viewer, you can follow the instructions in the User Manual under “Configurations and Settings” -> “Desktop Extension or Desktop Duplication (mirror) Settings in Display Control Panel” by clicking the link here:
https://forum.spacedesk.netuser-manual/#item_471
Thank you!
-
該回覆由 spacedesk Renz 於 2 years, 7 months ago 修改。原因: Adding email notifications for additional replies
Hi @shodan,
1. Maybe the coming out of full screen is still a bug in our Windows Viewer app which we cannot fix immediately.
This will take time to analyze and fix.
2. Command line parameter
Currently, spacedesk Windows 10 and/or 7 Viewer do not have command line to start up.
You can create a simple program that can auto-run and assign the position of each instances or maybe search for a third party application tool that can do this.
3. Connection via hostname
It should work, by setting it in the UWP Viewer settings -> Connection -> Start-up connect -> host name, type your host name.
Then on the next time you run the UWP viewer app, it will automatically connect to that host name.
Well it looks like i can send links to other image hosting which don’t have such restrictive file size as this forums but I’m unable to do so I have to write it with very compressed images. Because it looks like my older post weren’t added.
This issue still persists in latest version of spacedesk.
This is screenshot from iPad when connected to computer with Windows 10 using spacedesk: Win10.jpg
This is screenshot from iPad when connected to computer with Windows 11 using spacedesk: Win11.jpg
Both screenshots were made using settings of spacedesk client with custom resolution set to 1920×1080 but only on Windows 10 it looks like it should
Hello,
Spacedesk is a very useful application and I am working using it for a very long time
But I had a common problem since I’ve started using it. If I make a wireless connection (via android hotspot or windows wifi direct/hotspot) after some time it gets stopped, mainly the network stops working and gets disabled on every ways. Only the connection gets disabled which I made connection to spacedesk.
The problem for android hotspot is my windows Wifi is still connected to it but no spacedesk and other connectivity throughout that network. If I disconnect the wifi dongle and reconnect to USB port physically, it gets back.
The problem for windows mobile hotspot is after getting disconnected from spacedesk, the connection to android gets disconnected and when I try to reconnect using wifi list in android, it says disabled.
The uptime for spacedesk connection usually persists between 30 mins to 2-3 hours, but recently it couldn’t hold longer than 10-15 mins and which is really frustrating for me to handle. The connection doesn’t stop if I use USB tethering. But it is the same thing to use USB and primary monitor.
I checked the other forum topics but none helped. Spacedesk saying that I have Nvdia shadowplay enabled, but I have already uninstalled geforce experience and there’s still that error statement. If there’s any way to specifically disable the feature please let me know.
-
該主題由 Toslim33 於 2 years, 7 months ago 修改。
-
該主題由 Toslim33 於 2 years, 7 months ago 修改。原因:diagnostics report upload, had to separate file size
This evening i installed Spacedesk (v1037 BETA), and installed it perfectly with my phone, used it for a few hours and when i was done with it i closed the app and then proceed to close it on my desktop, the screen blacked out for a few seconds and then came back like this
Hello,
New tablet Xiaomi Pad 5 with updated version MUI 13 (android 11 RKQ1) doesn’t detect primary server. Last spacedesk app update.
Spacedesk working fine between PC on win 10 with last spacedesk working fine and my old tablet (also on updated version of spacedesk).
All deviced are connecter to the same wifi network.
Adding manually the IPP doesn’t work either (checked it was the good adapter interface)
So I conclude problem with android 11 / MUI 13 for this spacedesk version ?
Thanks