By the way, I found this on another forum:
By using this "trick" to bypass the weakness of Thinapp (it's unable to recognize the %ALLUSERSPROFILE%), it will randomly fail if Office is already installed or has been installed on the computer.
I think the source of this problem is the interpretation of the variable %Common AppData% by Thinapp.
Yesterday, I've found a way to perfectly workaround this weakness with a very good result:
1. Move the "Microsoft\OfficeSoftwareProtectionPlatform" folder from "%drive_C%\Documents and Settings\All Users" to "%Profile%".
2. Add the following text in HKEY_CURRENT_USER.txt:
isolation_writecopy HKEY_CURRENT_USER\Environment
Value=ALLUSERSPROFILE
REG_EXPAND_SZ~#2325USERPROFILE#2325#2300
Value=ProgramData
REG_EXPAND_SZ~#2325USERPROFILE#2325#2300
3. (OPTIONALLY) Move all the "%Common AppData%" content into "%Profile%" and edit all the %Common AppData% entries in package.ini
In the virtual environment, %ALLUSERSPROFILE% and %ProgramData% will be equal to the %USERPROFILE% which means that the common profile will be the user profile and it's not to Thinapp to intrepret and convert the %USERPROFILE% variable but to the Windows environment (and I think it's why it works better).
This operation is not a problem for a portable (or thinapped) application because "user files" or "all users files" have no sense.
So, you can move all the "%Common AppData%" files and folder into "%Profile%".
Now, I can launch a Thinapped Office 2010 on a computer with an Office 2010 product installed (if the "real" OSPPSVC service is closed, of course).
I hope it will help you!
Some guys were complaining that sometimes activation failed and they said this helped them.
What do you think..?
