"Microsoft Shared" misspelling, x64 Vista / W7

[Blín D'ñero]

Update.
When i started this thread I thought i had a huge problem by the horns, but apparently it is no problem at all (see last post).

---

Holy crap!
After installing Microsoft Office 2007, on a 2 weeks recent Windows 7 x64 installation.
Installing 3DMark Vantage, an "Error 1606" came up, that it "Could not access network location C:\Program Files (x86)\Common Files\microsoft shared\VC"....
No wonder, look here:



The "Microsoft Shared (with capitals) for Program Files (x86)\Common Files\" misspelling is all over the place.
There is no correctly spelled registry (sub-)key for that path.
Or maybe it is not case sensitive at all? But if it is, there are many corrections to do.





And many, many, many more (and not only Office keys)....all referring to a path that does not exist.
(strings referring to VS7DEBUG\mdm.exe amongst them)
And this is after Microsoft Visual C++ redistributable fully updated, on Windows Vista 64 SP2 and Windows 7 64-bit, and Microsoft Office 2007 installed (in Installation Options "Visual Basic for Applications" enabled) and also fully updated via WindowsUpdate.





So. A lot more corrections to do now... and i'm not 100% sure if it is even necessary to do them all. but i did it anyway.

I did this:
Open regedit and use "microsoft shared" as Find term (find term itself is not font-case sensitive).
Corrected all relevant paths that i found:
for
Program Files (x86)\Common Files\ the correct spelling is microsoft shared.
for
Program Files\Common Files\ the correct spelling is Microsoft Shared.

[Blín D'ñero]

HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{00000100-0000-0010-8000-00AA006D2EA4}\InprocServer32 does not allow modifying...
as do not
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{00000101-0000-0010-8000-00AA006D2EA4}\InprocServer32
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{00000103-0000-0010-8000-00AA006D2EA4}\InprocServer32
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{00000104-0000-0010-8000-00AA006D2EA4}\InprocServer32
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{00000105-0000-0010-8000-00AA006D2EA4}\InprocServer32
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{00000106-0000-0010-8000-00AA006D2EA4}\InprocServer32
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{00000107-0000-0010-8000-00AA006D2EA4}\InprocServer32
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{00000108-0000-0010-8000-00AA006D2EA4}\InprocServer32
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{00000109-0000-0010-8000-00AA006D2EA4}\InprocServer32

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{00000100-0000-0010-8000-00AA006D2EA4}\InprocServer32
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{00000103-0000-0010-8000-00AA006D2EA4}\InprocServer32
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{00000104-0000-0010-8000-00AA006D2EA4}\InprocServer32
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{00000105-0000-0010-8000-00AA006D2EA4}\InprocServer32
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{00000106-0000-0010-8000-00AA006D2EA4}\InprocServer32
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{00000107-0000-0010-8000-00AA006D2EA4}\InprocServer32
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{00000108-0000-0010-8000-00AA006D2EA4}\InprocServer32
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{00000109-0000-0010-8000-00AA006D2EA4}\InprocServer32

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{00000100-0000-0010-8000-00AA006D2EA4}\InprocServer32
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{00000103-0000-0010-8000-00AA006D2EA4}\InprocServer32
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{00000104-0000-0010-8000-00AA006D2EA4}\InprocServer32
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{00000105-0000-0010-8000-00AA006D2EA4}\InprocServer32
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{00000106-0000-0010-8000-00AA006D2EA4}\InprocServer32
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{00000107-0000-0010-8000-00AA006D2EA4}\InprocServer32
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{00000108-0000-0010-8000-00AA006D2EA4}\InprocServer32
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{00000109-0000-0010-8000-00AA006D2EA4}\InprocServer32

Also not the string values starting with %CommonProgramFiles(x86)%

[Blín D'ñero]

Goddammit already over 2 hours work, and still so many left:



Maybe not all are case sensitive...? But how can i know? I just correct ALL that i find. Hundreds and hundreds and hundreds...

Ironic seeing strings passing by like "Microsoft Shared Correction UI", or "\Program Files (x86)\Common Files\Microsoft Shared\VS7DEBUG\mdm.exe"

[Blín D'ñero]

Entire evening ruined.
Hopefully it was worth it.
After all this, the Repair installation of 3DMark Vantage went without issue.

Next: my other PC's, same job to do.

[Blín D'ñero]

New ones that are also wrong:
HKEY_USERS\S-1-5-18\Software\Microsoft\Windows\Shell\MuiCache:
@C:\Program Files (x86)\Common Files\system\wab32res.dll,-10100 (Data: Contacts) <--should be System
@C:\Program Files (x86)\Windows Mail\WinMail.exe,-225 <-- Windows Mail is not in 'Program Files (x86)' but in default 64-bit 'Program Files' (not that i use it anyway, but still)
@C:\Program Files\movie maker\dvdmaker.exe <-- Proper folder name is Movie Maker

..and a lot more...
For instance: many strings for C:\Windows\system32 (Data: Contacts) <--- doesn't exist on Vista x64 and W7 x64, should be System32 ....
... that don't allow renameing (unlike those in CLASSES_ROOT).

And i guess quicker would be to register via commandprompt all files inside Microsoft Shared and microsoft shared.

[Blín D'ñero]

An extra Microsoft Visual C++ 2005 Redistributable has again been installed, and i now have on Windows 7 (x64):



I think it was Call of Duty Warfare 2 i installed recently that auto-installed that extra VC++redist 2005 with it on 12/9.

Wondering if this is normal i found an explanation for this on microsoft devs forum:

MSI installers running on Windows 7, Vista and XP can install "side-by-side" assemblies. Assemblies can be COM components, or Win32 DLLs.
The concept behind "Side-by-side" assemblies is that several versions of the same DLL can exist on the system at the same time, "side by side".
In the past , updating shared DLLs with newer versions caused many application errors and lead to the so-called "DLL Hell". With Side-by-Side, each app gets the version of the shared DLL it likes best. These Side-by-Side files are stored under C:\Windows\winsxs ("SxS" is the common abbreviation for Side-by-Side).

Applications built with Visual C++ typically have a "manifest" which tells the application what specific side-by-side DLL versions are acceptable.
So when App1 goes to load msvcr80.dll, it will look in the first directory, for the version of msvcr80.dll it likes best. App 2 may look in the second directory instead, to find a specific version of msvcr80.dll it likes. If the app does not request a specific version, the Side-by-Side cache manager will load the "best" DLL, according to some internal algorithm. If an application mandates a specific version of a DLL in its manifest, and that version is not present on the system, then you will get an error, even though there may be several other versions of the DLL on the system.
This mechanism is designed to get past the problem of "DLL Hell"
[...]
The exact list of runtine versions you need depends on what applications you have installed, and what Runtime DLL versions they are mandating (if any). But apart from a small amount of disk space (these are not big files) there's not much overhead in having several versions of the Runtime installed. So you don't need to aggressively trim the list.

[Blín D'ñero]

Did a format and fresh install of Windows 7 x64.
This time i only registered the 64-bit version msdia80.dll, and did no spelling corrections in Registry. Now see how it goes.

I don't have Microsoft Office 2007 installed yet though. Installing and running Vantage didn't pop up any problem.