Hi @felipes1603,
1/4/5. We are not actually sure if USB tethering speed will depend on what type of cable and port you are using.
Based on our observation on our side, spacedesk performance (in USB tethering connection) is the same regardless of USB cable type and port.
We also don’t know if the network speed can be increased, we always get 425 Mbps speed on our side.
And even if we manage to increase the speed, spacedesk only supports 30-60 fps fixed in the settings.
2. This seems to be a Windows behavior.
There are some suggestions here that you might want to try:
https://superuser.com/questions/729305/prevent-windows-from-creating-new-network-names-when-tethering-with-android
https://answers.microsoft.com/en-us/windows/forum/all/usb-tethering-creating-new-names-each-time/3b360d02-578c-46eb-b155-1d899775f29b
3. It’s not yet finalized, but the Viewer Pro version will probably include some performance improvement/feature e.g. hardware accelerated image encoding, native USB cable connection support.
Hi @gopuri,
In a multiple viewer setup, touchscreen feature is only supported in one viewer app and the others will only get the single input mouse touch.
This is the current design of spacedesk.
Hi @chidochiki,
It is ready and working for one specific corporate customer configuration.
It will be integrated into public spacedesk version as soon as a business customer will request it and pay for it.
Hi @libo,
Thanks for sending the memory dump file.
Based on our analysis, the problem seems to be the USB driver used by the mobile phone for USB Tethering (Remote NDIS).
This is actually a known BSOD issue in spacedesk (with USB tethering connection), please check Troubleshooting -> Critical Errors -> Windows 10 Crash with BSOD (Blue Screen of Death) https://forum.spacedesk.netuser-manual/#item_483.
Can you check if there is maybe a newer version of this mobile phone USB driver (via Windows Update) and try to update?
PS: We have attached the dump analysis in case you want to check.
Hi @ibeerz,
Thank you very much for sending the diagnostic logs.
Based on the logs, you have Nvidia ShadowPlay/In-gmae overlay running on your primary machine.
Please disable this feature in Nvidia GeForce Experience, reboot then try again with spacedesk.
Hi @brad,
We don’t actually know if spacedesk supports Nvidia Surround feature, we have never tested it due to lack of resources.
For further analysis, could you please send us the diagnostic logs for this issue?
JUst follow the steps below:
– 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 (make sure to click Yes in the User Account Control box to proceed)
– try to connect your viewer app and reproduce the issue (please try with smaller resolution e.g. 1024×768)
– 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.
If possible, can you also maybe send us a short video while reproducing the issue?
spacedeskRuntimeDiagnostics
Hi @haveit,
Thanks for the feedback.
Could you please try this new test binary here: https://www.dropbox.com/s/nq8ex5oq48ka1rq/spacedeskWindowsVIEWER.exe?dl=0
Then check if it will work now on your secondary machine.
Hi @eauria,
Thanks for sending the debugview log file.
We were able to reproduce the same issue and verified that even without spacedesk driver installed on primary machine the issue is still happening, just plug a second monitor and try to project the OLP on the second screen.
This is probably a screen update issue on the OLP software with a transparent theme.
Hi @mortimar,
Apologies for not getting back to you.
We have checked dxdiag, we are not sure if it will help but maybe you can try the following:
1. update your Intel(R) UHD Graphics 620 driver, just download the latest driver from their website or via this
link https://www.intel.com/content/www/us/en/support/detect.html
2. We also noticed a Citrix Indirect Display Adapter on your machine, is it still active in your machine?
Can you maybe try to disable it temporarily?
And check is it will make any difference in the taskbar behavior when using spacedesk
3. Can you maybe try some of the suggestions here (especially #1): https://www.laptopmag.com/articles/windows-taskbar-wont-auto-hide
Hello. I don’t know if anyone is still having this problem, but I had it. I solved by deactivating window’s security’s real time security. While deactivated, I installed spacedesk and was successful!
I hope this helps anyone else having this problem.
Hello spacedesk-team,
I want to bring that up again.
Just updated to 1.0.40 on Win10 and using an Android Tablet with the latest app too.
Still having the issue with the broken taskbar not automatically hiding while using spacedesk connected through Wifi.
A few posts back I post the requested dxdiag file. Did that help?
Can you give me any other tips?
Can I help you with other inputs to get this fixed since only a reboot is helping.
Thank you very much.
Bye morT
I carefully read the document instructions, and then tried various ways to replace the USB program to replace the motherboard program.Upgrade to Microsoft 11 OS and then reduce the screen resolution refresh rate.During this period, I carefully observed the fluctuation of CPU memory and graphics card, and found that it had nothing to do with these three, sometimes simply moving the mouse can cause blue screen.Sometimes it can be used for three hours through the USB connection, during which time I use nearly 300MB of high-definition Blu-ray bandwidth and nothing happens, but when the mouse is moved, that is, when the operation is performed, then he will blue screen, sometimes 10 minutes. It will blue screen, and sometimes it will only blue screen after 3 hours. During this period, after 20 to 30 minutes, the sound and the picture will not be aligned, and then I will close the video software and reopen it. I also tried disabling spacedesk’s own mouse and keyboard controls to no avail. The blue screen keeps appearing.
-
该话题由
libo 于 2年、 5月前 修正。
OK, I set up Windows with the spacedesk/Galaxy monitor extending the Windows desktop, started OLP and displayed one song with debug collection on. I’ve also included a screenshot in the zip from the Galaxy of the session’s output. As you’ll see, not only is the OLP presentation screen not removed, the lyrics from each slide continue to overlay each other. Viewing the OLP output from a browser source in OBS reveals a black screen with lyrics in the lower third one slide at a time as expected. Attached in the debug info.
Hi @keyshawnokon,
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 (dxdiag.txt)
– spacedeskSetup.log file located in C:\Users\Public
– setupapi.dev.log file located in C:\Windows\INF
– a screenshot of the error during installation
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 @ahfeldma,
Ok, thanks for the feedback.
Could you please try the steps below after disabling your Malwarebytes and Norton Firewall:
– open the spacedesk Driver Console window -> Diagnostics
– if Debug View is not available, please click the download button first
– switch Diagnostic Collection ON (make sure to click Yes in the User Account Control box to proceed)
– try to connect your viewer app and reproduce the “Unable to connect” issue
– switch Diagnostic Collection OFF
– click Save All Information button
Then send us the updated diagnostic logs collected.
Hi @eauria,
Is the android version 1.1 or 11?
What is the native screen resolution of your Samsung Galaxy Tab A device?
For further analysis, please send us the diagnostic logs. Just follow the steps below on your primary machine:
– 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 (make sure to click Yes in the User Account Control box to proceed)
– try to connect your viewer app and reproduce the screen update 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 @haveit,
Thank you very much for sending the log file.
We are currently analyzing it.
Could you also please send us the dxdiag info of your secondary machine, just run the dxdiag.exe then click “Save All Information”, then save the output file (dxdiag.txt).
And can you quickly try to connect with HTML5 viewer on your secondary machine, just open a web browser e.g. Google Chrome then go to http://viewer.spacedesk.net/ and try to connect to your primary machine’s IP address.
Then let us know if you also get a black screen.
If it also did not work with HTML5 viewer, are you willing to help us further investigate the cause of the problem by checking the network packets (on both server and client side) using wireshark app?
Hi @leungzw,
We are not familiar with openwrt so we are not sure if this is blocking spacedesk.
Anyway, we are glad that it is now working on your side.
In case you have other spacedesk related concern don’t hesitate to contact us.
Hello, First off, I’d like to thank you for your community contribution. And if the least I can contribute is to reveal needed refinements in spacedesk, it’s a pleasure. I installed spacedesk to assist in the completion of a project involving Open Broadcaster Software and OpenLP, open source streaming and worship presentation software respectively. Anyway, I’m using spacedesk to provide a second monitor for OLP(OpenLP). I’ve created an OLP theme with a transparent background and a lower third display for lyrics. OLP starts and displays OLP’s presentation screen on the spacedesk second monitor, which is a Samsung Galaxy Tab A running Android v1.1. When activating a live presentation with this transparent background, the lyrics overly OLP’s placeholding startup screen on the second monitor. Feel free to ask for additional details.
Hello, so i’ve just started using spacedesk today, and when i decided to stop displaying on my second monitor, i clicked with 3 fingers on the touche pad as was mentionned, and then the screen froze on a black screen, but there was light on the screen. i couldn’t move mouse or anything, so i forced reboot. and now when i turn on my pc (which was a second monitor) it turns on but the screen stays black, with no light in it, so it’s like the screen doesn’t turn on at all, even when i enter bios.
Please help !!!
finally I found the problem was on the router2(IP:192.168.2.10) which is running a openwrt firmware.
After I remove this openwrt router out of the network spacedesk works fine.
maybe some openwrt feature is blocking some spacedesk traffic?
Hi @haveit,
For further analysis, could you please follow the steps below on your secondary machine
– download this spacedesk Windows 7 Viewer that we recently compiled here:
https://www.dropbox.com/s/onq88ky3gqx96e6/spacedeskWindowsVIEWER.exe?dl=0
– this executable file is the same as the version 0.9.37 (we only enabled a few more debug traces)
– then download the DebugView app here: https://docs.microsoft.com/en-us/sysinternals/downloads/debugview
– extract the DebugView.zip and run the DbgView.exe as “Administrator”
– make sure to check the Capture -> Capture Win32
– open the spacedesk Windows 7 Viewer .exe file that we sent to you, then try to connect (to reproduce the Display Off issue)
– there should be some “SA [xxxx:xxxx]…” traces printed in the DebugView screen, save it (as .txt file) and send it to us
Hi @haveit,
Thanks for the feedback.
Can you tell us which spacedesk Windows Viewer did you use?
Is it the Windows 10 Viewer app (from Microsoft Store)?
Or is it the Windows 7 Viewer app (Desktop Version 0.9.37)?
Hi @haveit,
Thank you very much for sending the diagnostic logs.
Based on the logs, you have Nvidia ShadowPlay/In-game overlay/screen recording enabled.
Please disable this via Nvidia GeForce Experience then reboot your primary machine.
After that please try again with spacedesk.
Hi @gennady46,
Thank you for your reply. Have you tried updating your server to the latest version (1.0.40)? If you haven’t, please try updating then see if you still encounter the issue. If the issue is still there after updating, please send us the diagnostic logs of your server machine by following these steps:
– 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 a viewer to the server to recreate the issue, then 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!
Hi @icarus,
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 on your next reply.
Hi @el_viejo,
For further analysis, could you please send us the error traces of the spacedesk Windows 10 Viewer upon app crash.
Please follow the steps below:
– download the DebugView app here: https://docs.microsoft.com/en-us/sysinternals/downloads/debugview
– extract the DebugView.zip and run the DbgView.exe as “Administrator”
– make sure to check the Capture -> Capture Win32
– open the spacedesk Windows 10 Viewer app then try to connect and wait for the crash to happen
– there should be some “SA [xxxx:xxxx]…” traces printed in the DebugView screen, save it and send it to us
Please also monitor the CPU, Memory and Network usage (if it’s high or low) in the task manager right before the crash, then let us know your observation.
after updating my main machine (windows 10) coming from spacedesk server 1.0.39 updating to latest 1.0.40 i notice frequent crashes of my spacedesk client (windows 10, spacedesk client 0.0.23.0 installed from ms store). this mainly happens when the main machine is locked for a while or in the moment the machine gets unlocked.
Hi @jgoo4414,
Thank you very much for sending the diagnostic logs.
However, the spacedesk traces in the DebugView.log file were inconclusive.
It did not capture the error traces during connection error.
Could you please try to get a new DebugView traces while reproducing the issue?
– open spacedesk Driver Console -> Diagnostics
– make sure that Debug View is available
– switch Diagnostic Collection ON (make sure to click Yes in the User Account Control box to proceed)
– try to connect your viewer app and wait for the issue to happen
– switch Diagnostic Collection OFF
– click Save All Information button
Hi @michal400,
Thanks for the feedback.
For further analysis, please send us the diagnostic logs of this issue.
Just follow the steps below:
– 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 (make sure to click Yes in the User Account Control box to proceed)
– try to connect your viewer app the shows black screen
– 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 @wayniec,
Thanks for sending the files.
Could you please quickly try the most recent spacedesk Driver v1.0.40 on our website https://forum.spacedesk.net.
If you still have the same issue, could you please go to C:\ProgramData\Microsoft\WDF, then send us the last 3-4 WudfHost_ext__xxx.dmp files.
Note: ProgramData folder is hidden by default, if you cannot find it in C:\ directory, just click the View tab in the File explorer, then check the “Hidden items” check box.
Please save all the files in one folder again, then right-click the folder -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.
Hi @pinklish,
Glad to know that you were able to fix it on your side.
In case you have other spacedesk related concerns, please don’t hesitate to contact us.
Hi @ahfeldma,
After adding the spacedeskService into your Firewall settings or disabling the Firewall, please try to open the spacedesk Console window and switch OFF-ON the spacedesk server.
Hi @pinklish,
Is it 5-10 seconds? Or minutes?
Can you specify which one is crashing on your primary machine side? Is it the spacedesk Driver Console window? Or the spacedeskService (verified via services.msc)?
For further analysis, please send us the diagnostic logs of this issue.
Just follow the steps below:
– 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 (make sure to click Yes in the User Account Control box to proceed)
– try to connect your viewer app and wait for the issue to happen
– 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 @michal400,
Which spacedesk Viewer did you use? Windows or Android?
And what is the current native screen resolution of your secondary device?
Hi @intelatombomb52,
Do you have VPN (Virtual Private Network) enabled?
Please also check if the client isolation on your WiFi router settings is enabled. If this setting is enabled, it will prevent direct communication between connected devices/computers.
For more info, please check Troubleshooting -> Network Connection chapter in the user manual https://forum.spacedesk.netuser-manual/.
Hi friends, I can’t use the spacedesk program that I’m actively using my tablet doesn’t see the computer anymore (they are connected to the same internet)
The ways I tried:
-I’ve formatted it.
-I deleted and installed it from the tablet and computer 2 times.
-I uninstalled the antivirus program.
-I gave you permission through the firewall.
-I haven’t tried manually.
Friends work with another wifi, but it doesn’t work on my own internet
Hi, I have a problem that when I connect any device to SpaceDesk on my PC, the screen that is connected stays black even though it does not write Connected display off. But the sound is transmitted but the screen does not. I have Windows 11 and SpaceDesk updated to the latest supported version.
Any advice?
Hi @jsclemmons,
We have released a new spacedesk Driver version 1.0.40 on our website https://forum.spacedesk.net.
It includes a potential fix for the blue screen crash during spacedesk installation. Please try it and let us know your result.
Looking forward to your feedback.
Hi @ahfeldma,
Thanks for sending the diagnostic logs.
We noticed that aside from Norton, you also have Malwarebytes.
Could you please try is to add “C:\Windows\system32\spacedeskService.exe” into the “Allow List” of your Malwarebytes and Norton settings to exclude spacedesk from all detections.
Hi @ange_laco,
Thanks for sending the requested logs.
It seems that uninstalling the old spacedesk HID driver is hanging.
This is a known issue in our older version, as a work around, please try to manually uninstall the old spacedesk Driver version on your primary machine before installing the latest version
For assistance, please check Uninstall on Windows Primary Machine -> Manual Uninstall (Troubleshooting Only) chapter in the user manual. https://forum.spacedesk.netuser-manual/#item_518
PS: Please make sure you do the Step 4: Uninstall spacedesk virtual HID Device (for Windows 10 only).
Hi @keith445511,
Thanks for sending the logs.
Based on the logs, it seems that you have a previous spacedesk Driver (v1014) installed on your machine.
Could you please try to uninstall it first via Microsoft Troubleshooter program which you can download 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_v1014_BETA.msi here: {8C330294-7E17-42D6-B17F-1D875427F066}
After that, please reboot your primary machine then try again to install the latest spacedesk msi installer from the website.
Hi @keith445511,
Thanks for sending the logs.
Based on the logs, it seems that you have a previous spacedesk Driver (v1014) installed on your machine.
Could you please try to uninstall it first via Microsoft Troubleshooter program which you can download 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_v1014_BETA.msi here: {8C330294-7E17-42D6-B17F-1D875427F066}
After that, please reboot your primary machine then try again to install the latest spacedesk msi installer from the website.
Hi @Spacedesk Lea,
unterfortunatelly this is all I got out of the diagnostic tool.
I use spacedesk Windows Viewer (Windows 10 Microsoft Store version)
Hi @serafa,
Could you please send us the diagnostic logs for this issue?
– 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 (make sure to click Yes in the User Account Control box to proceed)
– try to connect your viewer app and reproduce the Connected – Display OFF 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.
By the way, please also send us your secondary machine info:
– operating system (Android/iOS/Windows)?
– network connection type (wired/wireless/USB tethering/WiFi Hotspot)?
– native screen resolution
Hi @ahfeldma,
Do you have VPN (Virtual Private Network) enabled?
What is the current Network Profile on primary machine? Public or Private?
You can check it in Windows Settings -> Network & Internet.
For analysis, please also run spacedesk Driver Console -> Diagnostic, click “Save All Information”.
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 @ange_laco,
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 on your next reply. Thank you!
Hi @jsclemmons,
For further analysis, could you please send us the following:
– run dxdiag.exe on your primary machine, click “Save All Information”, save the output file (dxdiag.txt)
– spacedeskSetup.log file located in C:\Users\Public
– setupapi.dev.log file located in C:\Windows\INF
– most recent dump file (*.dmp) of your BSOD with spacedesk which is located in C:\Windows\minidump folder.
Please save all the files in one folder then right-click the folder -> Send to -> Compressed (zipped) folder, then attach the *.zip file in your next reply.
