Today I thought it would be a good idea to install some more apps on my Windows 7 machine. I had previously installed things like Office. The difference today is that it was straight after production activation (well an hour or so afterwards). I repeatedly got the same error :-
Error 22/01/2009 10:47:51 Application Error 1000 (100)
Faulting application name: msiexec.exe, version: 5.0.7000.0, time stamp: 0×49431c33
Faulting module name: ntdll.dll, version: 6.1.7000.0, time stamp: 0×49433e67
Exception code: 0xc0000005
Fault offset: 0×0007f6d6
Faulting process id: 0xdf4
Faulting application start time: 0×01c97c7ede31df1e
Faulting application path: C:\Windows\System32\msiexec.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 1d4f5f49-e872-11dd-9d8d-001641a9741a
I thought it was because I was installing over the network, so I tried the files locally. I tried other MSI’s, and had the same problem. I hunted around a little bit, and Windows then helped me after I sent the error report … it said :-
function expand( obj ) { if( obj.nextSibling.style.display==’none’ ) { obj.nextSibling.style.display = ‘block’; obj.firstChild.firstChild.src= ‘http://wer.microsoft.com/Responses/include/images/down.gif’ } else { obj.nextSibling.style.display = ‘none’; obj.firstChild.firstChild.src= ‘http://wer.microsoft.com/Responses/include/images/right.gif’ } }
|
Solve a problem with Windows 7 beta An issue with the Customer Experience Improvement Program (CEIP) client in Windows 7 beta is causing Explorer and some MSI-based installers to stop working properly. To solve this problem, follow these steps:
|
Low and behold … after that the installations are now working again !
, click All Programs, and then click Accessories.
In the User Account Control window, verify that Program name is Windows Command Processor, and then click Yes.