Pauline's community posts

Hello John,

Perhaps, it was some temporary glitch. I'm glad to hear that it works for you now!

I'll let you know once there's an update regarding the Shift key.

Hello John,

Yes, when you restart Host, Viewer will wait for it to restart and try re-connecting to it in the same session automatically.
Please try restarting your Viewer as well (make sure to fully exit it with File -> Exit) and see if this helps to fix the issue with the Windows key.

Let us know if this helps.

Hello,

Thank you for the provided details.

I'll forward this issue to our developers and we will test it in our environment to see if we can reproduce the issue and add a fix for it in our future updates.

I'll let you know when there are any updates on this issue.

Hello John,

Thank you for the clarification.

We will test this out in our environment to see if we're able to reproduce the issue and fix it in our future updates.

I'll keep you updated.

Hello John,

Thank you for your message.

Could you please let us know what happens now when you click Shift+Click and what is the exact expected result so that we could try to reproduce this?

Looking forward to your reply.

Hello,

Could you please let us know what View mode do you use when connecting, i.e. Stretch, Fullscreen, etc.? In addition, please double-check that the graphics cards on both computers are updated to the most recent version available. Does the issue occur only in this specific window or do you experience it somewhere else?

Looking forward to your reply.

Hello,

Thank you for your message.

Could you please try enabling the Capture alpha-blending windows option in the Connection Properties menu as described here and see if this helps to resolve the issue?

Let us know if this works for you.

Hello Trent,

Thank you for your message.

As per Microsoft support forums, this error code is usually caused by the graphics acceleration driver (usually related to an Intel Graphics Kernel Mode Driver). When you see this error message, it might be caused by the graphics card driver being unresponsive. In this case, you might try re-installing the latest driver directly from the Intel website.
In addition, you can also check if you're able to Roll Back the Graphics Card Driver - this option can be located in the Device Manager -> Display adapters -> Properties -> Driver tab. If you're unable to roll the driver back, you can try uninstalling it completely.

You can also try running the Deployment Image Servicing and Management (DISM) tool which fixes the Windows corruption error if there are any. Follow the steps as described here:
1. Press Windows+X.
2. Click on Command Prompt and select Run as administrator.
3. Type the command DISM.exe /Online /Cleanup-image /Restorehealth and press Enter.
4. Alternatively, in the Command Prompt window, type sfc/ scannow and hit Enter - this way the System File Checker will scan the machine for corrupted or missing system files and then try to fix them.

Alternatively, you can also try running the remote machine in Safe Mode as described here.

Hope that helps.

Hello Michael,

I'm glad to hear we were able to help and it works for you now!

Let us know if you have any questions or need our assistance.

Hello Michael,

Thank you for the clarification.

Yes, the password that is set up on the Host's side and the password that you save in the Connection Properties window must match in order for the connection to work. If you enable the feature to randomly generate a Host password while generating an installer, then you should receive an email with encrypted code that contains the access credentials. You can add this Host to your address book via the Add using code feature. This way, the correct password is automatically saved in the respective connection properties for a corresponding Host (each Host has a different password).
Please note that if you save the wrong password in your default connection properties (for example, the "password" password), you won't be able to connect to remote Hosts, since your Viewer will attempt to connect using the wrong password saved in the connection properties.
In this case, we recommend that you try adding Hosts to your address book via the Add using code feature as described in the guide linked above and see if this works for you.

Hope that helps.