The (default) value should be "Visio.Drawing.15" Update these keys HKEY_CLASSES_ROOT\.vsd and HKEY_CLASSES_ROOT\.vsdx to the following So the log of the short is verify the following keys are set to "Visio.Drawing.15" Here is a copy of the preferential user policy, if you are running an enterprise with AD and Group policy you can use the following to update the keys. "hkcu\software\Classes\.vsdx" the default value should be "Visio.Drawing.15" To fix it long term for all users was to use a policy to update the key for all users when they log on. I verified the key does not actually exist in the default user profile, so you cant fix it there. Using preferential policy because we needed a solution for new users, I set it to update this key to the correct value. I noticed this set to the wrong value of "vsdx_auto_file" vsdx, this led me to hkey_classes_root\.vsdx I found a heap of people with this issue, one of the fixes for older versions of visio was to update hkey_classes_root\.vsd (default with Visio.Drawing.15) I ran visio.exe with the switch /noreg "C:\Program Files (x86)\Microsoft Office\Office15\visio.exe /noreg" Net result is that visio repairs on every launch but never fixes the problem.Īnyways that's the problem and the reason behind it, the fix is below. vsdx is incorrect and tries to correct it with a repair, but the repair does not update they key for hkey_current_user\software\Classes\.vsdx that is actually causing the issue. So the visio on launch detects that the file association for. Hkey_current_user\software\Classes\ is always the winning key. The problem is that hkey_classes_root is actually the net result of hkey_local_machine\Software\Classes and hkey_current_user\software\Classes\, where vsdx exists in both locations, the HKLM value for me was actually correct. Why?īecause hkey_classes_root is a combination of the users file associations hkey_current_user\software\Classes\ (this is where the bad key exists) Unfortunately the msi repair does not fix the key, nor does uninstalling and re-installing update the key to the correct value. So the problem seems to come with visio wanting to register the file associations on launch, this causes a msi repair. This issue seems to have been in every version of visio while the fix varies on version.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |