All Things Microsoft > Microsoft Software
New M$ Spyware?
NeMeWaHa:
I noticed a major slowdown in the properties dialog for AVI files on my system and discovered that MSISIP.DLL, a signature handling component of the M$ installer, was scanning the whole files for encrypted signatures!
This file is installed with many M$ patches and third party programs as a part of the installer utility. That it starts to search my media files on it's own when I'm not actually installing something leads me to suspect another sleazy attempt to sneak spyware into everyone's system.
In any case, it slows things down so much that I advise you find that file and rename or delete it. It is not needed for anything until you are actually installing software or one of the many M$ patches and bugfixes, and will be automatically replaced by the installer whenever you need it for legitimate installations.
ForceSphere:
quote:From http://www.charliesources.net/:
Several readers asked for assistance with a Windows 2000 Service Pack 3 (SP3) setup failure that produces the error message "An error in updating your system has occurred. When you click OK, Windows is not upgraded to SP3 and you can no longer install programs that use the Windows Installer (.msi packages)."
When this error occurs, any later attempts to use Windows Installer to install software (e.g., SP3, a Microsoft Office update, or any software that uses winstall technology) will produce a message that says "The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed...."
This failure occurs because the latest version of Windows Installer (version 2.0.2600.2), packaged with SP3, doesn't install or run on a system on which the Distributed COM (DCOM) default impersonation level is set to Anonymous. Even worse, after an SP3 installation fails, the system retains the SP3 version of Windows Installer, but the installer won't function properly even if you restart the upgrade. To reinstall SP3 successfully, you need to change the DCOM impersonation level to Identify, and you need to delete the problem Windows Installer file (msisip.dll). To change the DCOM impersonation level, open a command prompt and type
dcomcnfg
If some objects aren't registered, the command will prompt you to register them. Then the utility displays the DCOM Configuration Properties window. Click the Default Properties tab, change the setting in the Default Impersonation field to Identify (click the down arrow for this field to view all valid settings), and click OK to exit.
To delete the problem Windows Installer file, locate and delete (or
rename) the file \%windir%\system32\msisip.dll. After taking this corrective action, you should be able to complete an SP3 upgrade.
--- End quote ---
that may clear some things up for you
NeMeWaHa:
I know about the SP3 bug, posts about it are all over the place.
Now tell me what that has to do with a piece of the M$ installer suddenly adding itself silently to the properties dialog of AVI files and secretly scanning whole AVIs for encrypted signatures? :D
xyle_one:
fuck it. try this fix
mobrien_12:
quote:Originally posted by NeMeWaHa:
Now tell me what that has to do with a piece of the M$ installer suddenly adding itself silently to the properties dialog of AVI files and secretly scanning whole AVIs for encrypted signatures? :D
--- End quote ---
My guess is that MS bundled DRM in with the installer. I don't know for sure, but it's certainly their style.
Navigation
[0] Message Index
[#] Next page
Go to full version