Jump to content
cc1158

have to unlock program every time i use

Recommended Posts

There are two possibilities... the Windows 8 issue or a registration issue. Here is the fix for the Windows 8 issue.

 

Windows 8 has a 'feature' that didn't occur in earlier operating system versions.

When you run as a Standard user and unlock TMG7 and TMG8, the program does not have the permission to write the registration information to the Registry, so the information is virtualized and written to the registry VirtualStore.

With WinVista and Win7, this worked fine.

Windows 8 comes along and periodically purges the registration information from the registry VirtualStore. That is why the program is locked again.

%%%%%%%%%%

The solution...

Step 1) You need to delete the registry key containing the virtualized information. This step is required for the solution to work.

On my system, the registry path is:
HKEY_USERSS-1-5-21-280371975-2347893702-1721369835-1000_ClassesVirtualStoreMACHINESOFTWAREWow6432NodeWholly
Genes SoftwareThe Master Genealogist V7
and
HKEY_USERSS-1-5-21-280371975-2347893702-1721369835-1000_ClassesVirtualStoreMACHINESOFTWAREWow6432NodeWholly
Genes SoftwareThe Master Genealogist V8

Your registry path(s) will be something similar.

Step 2) After deleting the registry key, you need to run TMG ONCE as Administrator and unlock the program.

Right-click on your TMG desktop shortcut and select 'Run as Administrator' to start TMG and then unlock. After unlocking, exit TMG.

Step 3) After the above steps, you can run TMG as a Standard user and the registration information will no longer be lost.

 

%%%%%%%%%%

 

If that doesn't work, I'll add the fix for the registration issue.

Share this post


Link to post
Share on other sites

Contact support (support@whollygenes.com) and see if they can walk you though it. In the meantime, you might try another possible fix. Rightclick on your TMG v8 icon on your desktop and select 'Run as Administrator.' Do this one time only.

 

Virginia

Share this post


Link to post
Share on other sites

That is good. I hope it is just not a temporary fix. Keep us posted. Again, you should run as Administrator this one time only, and note that 'running' as Administrator is different from 'logging in' as Administrator - which you should not do at all.

 

Virginia

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×