ProfileUnity 6.5 - ProfileUnity client startup fails after upgrading from 6.0 to 6.5

Product: ProfileUnity

Product Version: 6.5+

Expires on: 365 days from publish date

Updated: October 20, 2015



After upgrading ProfileUnity from 6.0 to 6.5, the client startup fails while the user is logging in.



1. During the logon,  ProfileUnity splash screen may show an older version of ProfileUnIty being executed (if Profileunity is installed in the base image).

2. If the ProfileUnity client is not installed in the image, the ProfileUnity splash screen may not show at all, or may only load certain settings and disappear quickly.

3. The following information may appear in a startup log after logon (you can find logs locations here)

2015-10-09 15:56:11 [1] FATAL - Os: Win7
2015-10-09 15:56:11 [1] FATAL - Version: 6.0.5394 b462ddd
2015-10-09 15:56:11 [1] FATAL - Could not load type 'LwL.ProfileUnity.Client.Framework.Common.IVhdExeCommand' from assembly 'LwL.ProfileUnity.Client.Framework, Version=6.0.5394.0, Culture=neutral, PublicKeyToken=null'.
at System.Signature.GetSignature(Void* pCorSig, Int32 cCorSig, RuntimeFieldHandleInternal fieldHandle, IRuntimeMethodInfo methodHandle, RuntimeType declaringType)


Possible Cause:

This is caused by a leftover DLL from version 6.0 that conflicts with 6.5. ProfileUnity 6.5 does not use this DLL, but if it is present, 6.5 will attempt to load the DLL. 

When you use the "Deploy Client Tools" option in the ProU console to overwrite files in the NETLOGON\ProfileUnity directory, the overwrite option does NOT delete this DLL, so the file will be left behind.


Possible Resolution(s)



Delete or rename "lwl.profileunity.client.framework.dll" in the netlogon\ProfileUnity folder.



Remove all files in the ProfileUnity folder except the license files, .INI files, and any other customer-created files such as scripts, then deploy the client tools again from the console. Note: Please make a backup of the ProfileUnity folder first.




Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Article is closed for comments.