Search Results for 'X'

[Motto5476]

Attached the generated spacedeskmsi_trace.txt as per instructions

Attachments:

You must be logged in to view attached files.

[spacedesk Lea]

Hi @motto5476,

Thanks for sending the logs.

For further analysis, please download the spacedeskMsiTraceGenerate.zip here:
https://www.dropbox.com/s/vr17lj6n63k52rh/2022_spacedeskMsiTraceGenerate.zip?dl=0
– extract the zip file
– copy the most recent spacedesk msi installer inside the folder then click the get_trace.bat
– the script will prompt you to enter the msi file name then press enter
– it will run the spacedesk installer until you encounter the error
– please send the spacedeskmsi_trace.txt generated inside the folder

PS: We moved your comments in a separate topic to avoid confusion.

[Motto5476]

Attached zip-file, excluding – spacedeskSetup.log file located in C:\Users\Public – which could not be found

Attachments:

You must be logged in to view attached files.

[Motto5476]

On my laptop it installed just fine, but on my desktop I’m getting the exact same error message as @Masteris. Has this problem been solved in the mean time?

[spacedesk Lea]

Hi @abossart,
We have received the video file, thank you!

Based on the video, this is the expected behavior when you mirror your primary display and secondary display.
If auto-rotation is enabled, then it will auto rotate the primary display once you rotate your secondary display because it is in mirror/duplicated mode.

If you don’t want the primary display to rotate, then you just disable the auto rotation.

[spacedesk Lea]

Hi @hhh,
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 wait for the issue (error code) 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.

[gennady46]

Never mind, I had to system update my PC and re-install spacedisk, everything is working, Ihave tested an application, is working fine, except a small bug, but it is not on your end.

Thanks so much, best regards, the issue is solved.

[spacedesk Lea]

Hi @abossart,

2. Can you please try the following:
– open spacedesk Driver COnsole -> Control -> Clear Windows Display Settings
– switch OFF the auto-rotation in the viewer settings before connecting

3. spacedesk Server is always ON and set to auto-start (at system boot) by default (unless you manually switch OFF the spacedesk status and uncheck the auto-start check box in the spacedesk Driver Console configuration).

[abossart]

Feature full software to mirror PC display on my iPad 11 iOS 15.4.1. I’m using for presentations a free stand for the IPad. So I need to turn the iPad by 180 degree. The display is then upside down on the iPad. If I set alternatively the auto-rotation feature it turns also the display of the PC and you can’t read the PC display anymore. Would be could if you could fix that. If one rotates the iPad the display should also rotate. But the PC display should always stay firm and not rotate. Thanks if you can help!

[abossart]

Hi

Working on a PC with iPad 11 as 2nd screen. When being in a PowerPoint presentation and being in Presenter Mode on PC and moving another open document (eg WORD or anz other) to the 2nd screen (iPad) it can be viewed well on the iPad but the cursor doesn’t move to the iPad screen. So the iPad can’t really be used in Extended Mirroring mode.
Would be great if you could fix it.

Thank you!

Albert

[opensorce]

Downloaded Spacedesk and ObjectDock ($5) for the sole purpose of creating a persistent app and shortcut launcher to use on a small tablet.

The tablet is low hardware Onn tablet with Android Go ($50 at Walmart). I installed Spacedesk and it behaves as a third monitor. Such great software! Setup is basically effortless. I couldn’t believe how easy this setup was.

The PC is a Ryzen 5 system with Windows 11.

I installed ObjectDock on the the PC and setup a tabbed dock (one tab) with shortcuts to various apps. Because of Spacedesk The touchpad works as it should and it’s the perfect touchpad app launcher for my rig. Very handy and worth every penny!

Pictures: https://ibb.co/3pwqGsF

[Luiz Antonio]

Olá
Segui as orientações enviadas e a conexão ficou perfeita.

Obrigado pelas rapidez no envio das orientações.

Abraços.

[spacedesk Lea]

Hi @luiz-antonio,

Have you tried adding the spacedesk in the exception list of McAfee Firewall?
If not yet, please try it.
Just open your McAfee Firewall settings, click Ports and System Services then click the Add button.
System Service Name: spacedeskService
Local TCP/IP Ports: 28252
Local UDP Ports: 28252

For reference, please check https://forum.spacedesk.netwp-content/uploads/2022/04/McAfeeFirewallSettings-spacedesk.jpg

[spacedesk Lea]

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.

[gopuri]

Ah dam. Hopefully it gets expanded to 2+ at some point.

[libo]

The latest BSOD showed ntoskrnl.exe was missing, then DirectX Repair Tool 4.1.0.30770 Standard Edition was patched with a software.There are 180 file bugs patched ；The system is up to date, should the then DirectX Repair Tool be built into the installer?

Attachments:

You must be logged in to view attached files.

[spacedesk Lea]

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.

[spacedesk Lea]

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?

[spacedesk Lea]

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.

[spacedesk Lea]

Hi @alfredo_c and @jamessprag,

Thank you very much for sending the requested screenshots.

Please try all of our suggestions below:

1. We have done a quick research and found a quite similar issue in the lenovo forum site.
Could you please try updating your Yoga C640’s GPU, Intel Chipset, Intel Sensor Hub and Yoga Mode Control Application drivers as suggested posted by a Lenovo support here: https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Yoga-C640-13IML-Touch-screen-not-working/m-p/5095730?page=1#5413877

2. Open the Device Manager the try to disable-enable the touch device underneath Human Interface Devices.

3. On Device Manager, please try to reinstall the devices underneath “Other Devices”.

4. Run system file checker to repair missing or corrupter system files. Just run Command Prompt as Administrator then type the command: sfc /scannow
reference: https://www.windowscentral.com/how-use-sfc-scannow-command-fix-problems-windows-10#sfc_repair_windows10

[spacedesk Lea]

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

[morTimar]

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

[eauria]

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.

[spacedesk Lea]

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.

[spacedesk Lea]

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.

[eauria]

My apologies, old eyes. Android v11, native res: 1200 x 1920. I will get you the debug info ASAP. It’s 11:58 CA. time. Beauty rest required. BTW, 40 years around the IT biz. Knowledge is power. You can save time on basic instructions.

[spacedesk Lea]

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.

[spacedesk Lea]

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?

[eauria]

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.

[spacedesk Lea]

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

• This reply was modified 2 years, 5 months ago by spacedesk Lea.
• This reply was modified 2 years, 5 months ago by spacedesk Lea.

[haveit]

From the server computer it is (Windows 10 64x Server) and computer №2 is (Windows 7 Viewer app (Desktop Version 0.9.37)).

[spacedesk Lea]

Hi @michal400,
Thanks for sending the new diagnostic logs, unfortunately the DebugView log file is missing.
Please click the Download button beside the DebugView first before switching the Diagnostic Collection ON.

– 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

[haveit]

Hello again! Unfortunately, this did not give the desired result. Еverything remained unchanged. Nvidia overlay was enabled, screen recording and instant replay were off. I disabled the overlay and disabled nvidia experience completely – no result. I made new logs and sent them to you. Thank you for not keeping me waiting for an answer.

• This reply was modified 2 years, 5 months ago by haveit.

Attachments:

You must be logged in to view attached files.

[spacedesk Lea]

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.

[kordula2@gmail.com]

Thanks!
I cleared windows settings
And then it was fixed!

Again thanks for a VERY good product.

Have a nice summer

Hans

[spacedesk Renz]

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!

[spacedesk Lea]

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.

[spacedesk Lea]

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.

[michal400]

Finally, I got to it, I did it exactly as you told me so I attach a .zip file with diagnostics to this text.

Attachments:

You must be logged in to view attached files.

[spacedesk Lea]

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

[spacedesk Lea]

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.

[michal400]

Of course, on a PC with Windows 11 version of Windows Server. My Android device has a resolution (if I remember correctly) of 800×600 and 60Hz.

[spacedesk Lea]

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.

[spacedesk Lea]

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.

[spacedesk Lea]

Hi @wadewilson,

Thanks for the feedback.
We have analyzed the DebugView you sent and able to reproduce the black screen issue on our side.

This issue was caused by the current screen resolution pitch limitation in the current Windows 10 (Microsoft Store) version, Android (Google Playstore) version and iOS (Apple App store) version.
This limitation will be removed soon.
But for now, you can use the Windows 7 (Desktop version) Viewer and it should work with your 5120×2880 client screen resolution.
Or you can still continue to use the Windows 10 version of the Viewer app and just make sure that the client resolution width will not exceed 4096.

[pinklish]

It turned out it was just a weird issue with my driver that I was able to fix with a setting in my computer. Thank you for your help anyways though! 🙂

[spacedesk Lea]

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.

[kor_ez]

When Windows 10 is used in portrait mode, the tablet connected screen cannot rotate in portrait mode.
So, I need a fixed portrait mode. For example, 90 rotations

[yuan]

I never thought that space-desk causes this wsl bug. I checked all the information I could find on Internet, but it worked until I saw this.
To express my appreciation, I register an account and write these words.
Thank you, guys!! Repairing Hyper-V drivers helps my life!!!

And remember, if you want to use wsl2, preparing virtualisation drivers is necessary when you ensure you have enabled all the virtualisation features.

[spacedesk Lea]

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.