The registry errors exist even with a clean install of Windows 7 and Office 2007 on a new hard drive on a Stand-alone computer that is not connected to a network (even some of Windows/Office TTF files have registry errors).
These registry errors are created in the absence of any anti-virus software, in the absence of any system utilities (no defrag, no disk cleanup utilities...other than native Windows utilities) and no registry cleaners, and the errors are always in the same registry keys.
Microsoft Tech Support worked with me (frequently connected by EasyAccess Remote control) and verified that:
- A rootkit virus is not the source of the problem - scanned with Kapersky anti-root kit utility and, also, the problem exists on a clean install on a new (boxed) hard drive.
- A virus or other malware is not the source of the problem - scans included Norton 2010, Malwarebyte's anti-malware, AVG (free), Avast (free), Microsoft Security Essentials and Live OneCare on-line Security Scan
- Hardware is not the cause of the problem. I found the problem on 16 computers of all varieties (OEM and clean builds), Microsoft found the problem on at least 4 or their tech support computers, and friends back in Illinois (2 public libraries and one museum) found the registry errors on their computers. The errors occur on computers with a single hard drive or dual hard drives, different types of processors, different BIOS, different memory configurations, etc.
- One anecdotal comment: MS Tech Support was unable to find the registry errors until they "unchecked" the "Match whole string, only" option in the Edit/Find window.
Issues that are consistent across platform/operating system/hardware are:
- The registry errors are generated progressively as additional software or updates are installed (The initial install of Windows does not create any registry errors "of this type") The first registry errors occur after Microsoft Office or Windows updates are installed (independent of installation order).
- The errors are predominately (maybe exclusively) with files related to graphical and other media file types and applications using these file types
- The registry errors do not seem to be generate by Browser add-ins. For example, Adobe Acrobat Reader generates registry errors, but Adobe Flash Player and Adobe Shockwave do not generate registry errors.
I do not blame MS Tech Support for bailing out on me on this Service Request. I think we eliminated every obvious (and some esoteric possible sources).
The last interaction I had on this issue was when the support request was elevated up to the Windows 7 Development Team. After one phone call from the Development Team (they verified the registry errors were present on their computers) in which they said they would be back to me in approximately a week (4 months ago), no progress has been made on the issue.
You have suggested some issues that I need to check out, but my conclusion is that the source of the registry errors are the MSI files used to install the Microsoft applications and updates and the MSI files used to install 3rd party, media file related applications.
My problems running the 3rd party software (Roxio and Adobe PhotoElements) were solved by manually editing the registry errors (C?\<path statement>) with a valid data value (C:\<path statement>)...about 750 total for Windows and these applications. I had blisters on my fingers from the repeated key strokes to deleted and paste in the correct C:\ !
Hope I haven't bored you to tears. I readily admit I'm a bit compulsive when I can't understand or find a solution to a computer issue.