Shrewsoft VPN client - can't open Access Manager


Shrewsoft VPN client - can't open Access Manager

Problem


Access Manager is not visible
Occurred after adjusting using dual monitors.
Reinstall does not fix the issue.


The Fix


Use regedit to rename or delete the following key:
HKEY_CURRENT_USER\Software\ShrewSoft\vpn\user

Had a look around the Shrewsoft support site - nothing useful in there to fix this problem.




Comments

  1. AnonymousJanuary 10, 2019 at 2:54 AM

    You sir, deserve a cookie !
    Thank you

    ReplyDelete
  2. UnknownJune 18, 2020 at 7:49 AM

    OMG!!! You have no idea how long I've been struggling with this! Thank you for the fix!

    ReplyDelete
  3. Matthias H.August 8, 2020 at 2:56 AM

    I had to delete the complete ShrewSoft entry in HKEY_CURRENT_USER\Software\ to be able to access the management window again.

    ReplyDelete
    Replies
    1. FrankJuly 9, 2021 at 11:10 PM

      Same here, worked after deleting the whole Shrewsoft entry.

      It just recreates the entry after you launch the program again in case anyone is worried about deleting it.

      Delete
  4. SamvatsarMay 24, 2021 at 2:59 AM

    Thank you so much for the help!

    ReplyDelete
  5. AnonymousMarch 28, 2024 at 9:59 AM

    Thank you, thank you! This problem is a regular occurrence for a user who normally uses an external monitor and then attempts to use this without the external monitor. Shrewsoft seems to remember its position on the external monitor and open there, even though it is not present. We have been going crazy trying to figure out how to resolve it. Many thanks!

    ReplyDelete

Post a Comment

Popular posts from this blog

Server Manager Refresh completed with one or more warning

The system cannot access one or more event logs because of insufficient rights The Problem: Configuration refresh message. The system cannot access one or more event logs because of insufficient rights, file corruption, or other reasons. For more information, see the Operation channel in the ServerManager-ManagementProvider error log on the target server. Problem occurred on Server 2012 servers that have been upgraded to Server 2012R2 servers. Servers are also clustered. The Solution: Following the event logs leads to a few registry keys. You can eliminate the messages by: 1. Export the following registry keys (for safety) 2. Delete the following keys: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-DxpTaskRingtone/Analytic HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-IME-Roaming/Analytic HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-IME-SCDICCOMPILER/Analytic HKLM\SOFTWARE\Mic...
Read more

Event ID 122 Access to Drivers on Windows Update Blocked by Policy - Fix Here

Image
Access to drivers on Windows Update was blocked by policy EventID:122 errors appearing on Windows Server 2012 Hyper-V host.  “Device Setup Manager” service. There is a scheduled task that runs each night in “Microsoft | Windows | Device Setup” called “Metadata Refresh”.  When that task runs it causes the “Device Setup Manager” service to start, and that’s what is causing the messages.  If you look in the Event Viewer under “Application and Services Logs | Microsoft | Windows | DeviceSetupManager | Admin” and filter on Event ID 122 then you can see the entries. The “policy” that is causing the block is actually the Device Installation Settings.  SOLUTION Use the search in the Control Panel window and look for “device installation” When that window opens, you will see the settings that define the “policy” If you change the setting to “Always install the best driver software from Windows Update.” then the Even...
Read more

Hyper-V failed to enable replication on the Replica server for the Virtual Machine

Hyper-V is not in a state to accept replication on the replica server for virtual machine   Message appears at the end of the replication Wizard. A replica for this virtual machine had previously existed on the Replica server. Cause The previous successful or unsuccessful replicated virtual machine may be still exist at the replica server.   Solution Remove the old virtual machine at the  replica server and enable replication again.  Yes this pushes a fresh replication to the replica server. Additional notes Under the details of the error message on the source server a Virtual machine ID is listed, and using this ID to find the replication files from the previous replication on the Replica server (under \Virtual Hard Disks\Hyper-V Replica\Virtual hard disks\<ID>\ and under \Virtual Hard Disks\Hyper-V Replica\Virtual Machines\<ID>. These files may be locked while a previous replica exists on the Replica server
Read more