Windows 7 Problem Solving: Crashing Installers and Updates

Article by George Norman (Cybersecurity Editor)

on 21 Jan 2009

Testing the first Beta version of Windows 7 , the next iteration of the Windows OS, does not go without a glitch, hence the “testing” and “Beta”. Besides getting the occasional BSOD (blue screen of death) , some Widows 7 Beta 1 testers are also reporting problems when running updates or during the install process for various applications.

The issue even occurs when running Windows Update and apparently the source of the problems is to be located with the Software Quality Management Client (SQM) which is also known as the Customer Experience Improvement Program (CEIP). Some may call it ironic, but I wouldn’t go as far as to say Windows 7 is a bad piece of software. Keep in mind that this is an early Beta build, and there is still some way to go until Microsoft releases the final version of the Windows 7 operating system.

Several workarounds are available for this problem, including one issued by Microsoft.

Workaround no. 1 – Disable CEIP: Run -> type in gpedit.msc -> Computer Configuration -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication Settings -> double click Turn off Windows Customer Experience Improvement Program.

Workaround no. 2 – Access the Registry Editor (Run, type in regedit) and locate HKey_Local Machine -> Software -> Microsoft -> SQMClient -> Windows -> DisabledSessions. Delete every string value apart from Default value. Renaming “MachineThrottling” with “_MachineThrottling” in the above workaround is also a viable option. Also, here is how to put the Run command back in the start menu, as it was in Windows XP.

Workaround no. 3 – the Microsoft proposed one:
- Copy the following: HKLM_SOFTWARE_Microsoft_SQMClient_Windows_DisabledSessions /va /f (Please note that due to technical reasons I've used _ instead of the backslash key, so you should replace _ with backslash).
- Start -> All Programs -> Accessories -> right click “Command Prompt” and select “Run as administrator”
- Check that the program is named “Windows Command Processor” in the UAC window. If it is, click “Yes”.
- Hover your cursor over the black colored area of “Administrator: Command Prompt” and right click.
- Paste the command from step 1.
- If at this point you get an error message, mainly “ERROR: Access is denied” it is because you did not properly follow step two (where you have to select “Run as administrator”).
- Close “Administrator: Command Prompt window”


Latest News


Sony's 'Attack of the Blockbusters Sale' Slashes Prices in Half for a Ton of PS4 Games

17 Aug 2017

How Samsung's New T5 Compares to the Old T3 Portable SSD (Infographic)

17 Aug 2017

See all