Une mise à jour silencieuse que Microsoft a déployée largement en juillet et août empêche le dispositif de « réparation » de Windows XP d'accomplir avec succès.

Depuis que le téléchargement récent de la compagnie de Redmond du nouvel appui classe pour la mise à jour de Windows, les utilisateurs de la fonction de la réparation de XP ont ne pu pas installer les dernières 80 pièces rapportées de Microsoft.

Les installations réparées de XP ne peuvent pas être mises à jour

La difficulté se produit quand les utilisateurs réinstallent les dossiers de système de XP en utilisant les possibilités de réparation trouvées sur les disques compacts-ROM véritables de XP. (Le dispositif n'est pas présent sur des « CD de restauration.  ») L'option de réparation, qui est typiquement utilisée quand XP pour quelque raison devient unbootable, roule beaucoup d'aspects de XP de nouveau à un état primitif. Il élimine beaucoup de mises à jour et pièces rapportées et place l'Internet Explorer de nouveau à la version qui s'est à l'origine transportée avec le logiciel d'exploitation. (plus…)

mises à jour automatiques, Internet Explorer, Microsoft, logiciel d'exploitation, pièces rapportées, compagnie de redmond, réinstallez le xp, réparez les possibilités, réparez la fonction, réparez les fenêtres, dossiers de système, examinez la machine, Windows, emplacement de mise à jour de fenêtres, xp

Je suis endetté à l'excellent site Web de secrets de Windows pour des nouvelles d'un développement alarmant août passé impliquant Windows XP et Vista installant silencieusement les dossiers exécutables, quoique les utilisateurs aient neutralisé les mises à jour automatiques. Ainsi des dossiers du prix neuf ont été identifiés, il peut y avoir plus, et tandis que les dossiers semblent être bénins il soulève la question très sérieuse au sujet des chargeurs de Microsoft sur des PCs sans connaissance ou permission d'utilisateurs.

The file downloads occur when users select the ‘Let me choose when to install or notify me but don’t automatically download or install’ option in Security Centre. The revelation appears to have embarrassed Microsoft into issuing an explanation and guarded apology, which basically says that whilst deselecting Automatic Updates does indeed stop any new updates, it doesn’t stop Windows Update updating itself. (more…)

apology, automatic updates, executable files, microsoft, revelation, security centre, silently, Windows, windows update, windows updates

It’s important to note that there is no reason to remove or roll back the updated support files that Windows Update may have installed on a PC. There’s no evidence that these files are harmful or cause any software conflicts.

Furthermore, if you use a corporate patch management solution, such as Microsoft’s WSUS (Windows Server Update Services), you circumvent Windows Update and no files will be installed by WU.

But if you’re an individual or a small business using Windows Update (or its enhanced sibling, Microsoft Update), you may be concerned about Microsoft installing patches before you’ve had a chance to research their reliability. In that case, you can completely turn off the Automatic Updates Agent, thereby preventing updates or even notifications from occurring. (more…)

automatic updates, balloons, cause windows, computer, launch windows, microsoft patches, microsoft update, software conflicts, support files, taskbar tray, vista, Windows, windows update, wsus, xp

Just received the following that is related to the SVCHOST issues that I’ve written about in the past…

MS has released “Microsoft Security Advisory (927891) - Fix for Windows Installer (MSI)” that’s not really a direct security concern, but actually addresses concerns that might prevent people from getting critical security or other updates.

As previously mentioned, it involves MS KB 927891 - “You receive an access violation error and the system may appear to become unresponsive when you try to install an update from Windows Update or from Microsoft Update“, and the current revision of the article (8.0) states “This fix is one component of a two-part fix that includes a Windows Update client software update. These updates will be deployed automatically using Windows Update in May 2007 and June 2007.”

Again, this update is one of two that need to be applied to fully address the issue. The other update is version 3.0 of the Windows Update Client Software, available from MS KB 932494, “When you use Automatic Updates to scan for updates or to apply updates to applications that use Windows Installer, you experience issues that involve the Svchost.exe process“.

One

…

Previously (here and here), I’ve written about isolating shared services so that they run in their own process, with a specific focus on the Windows Update Automatic Updates Service (wuauserv) that typically runs in the NETSVCS SVCHOST.EXE instance. One thing that can be done once this is accomplished is to lower the priority of the process so that when the service winds up consuming 100% of the CPU, the system doesn’t become unresponsive.

Since we’re dealing with a service, setting the priority of such a SVCHOST.EXE process can become problematic - the service may already be running, or, because it is a service, it is not started as non-service processes are, so one is not able to use START / [LOW NORMAL HIGH REALTIME ABOVENORMAL BELOWNORMAL] to impose a priority when the process starts. One can use a utility like Task Manager or Process Explorer to set the priority of a process on an ad hoc basis, but when the service restarts or the system reboots one has to remember to set the priority again.

Though not an ideal solution the following scripts (VBS using WMI, and PowerShell) can be used to set the

…

In the past, I’ve written about both high CPU utilization by SVCHOST.EXE as well as the 0×8ddd0009 Windows Update / Microsoft Update error, so I thought I would mention this…

MS KB 932494 (When you use Automatic Updates to scan for updates or to apply updates to applications that use Windows Installer, you experience issues that involve the Svchost.exe process) references problems that are addressed by MS KB 916089 (FIX: When you run Windows Update to scan for updates that use Windows Installer, including Office updates, CPU utilization may reach 100 percent for prolonged periods) and MS KB 927891 (You receive an access violation when you try to install an update from Windows Update after you apply hotfix package 916089). However, even after applying the patch associated with 927891 (which replaces the patch associated with 916089), 932494 indicates that the following problems remain:

1) Certain 100 percent CPU issues are still present when you use the Svchost.exe process.
2) An access violation may occur in the Svchost.exe process.

I (as well as others) have speculated in the past that 916089 (and its succedent patches) can also help with the 0×8ddd0009 error…