J'ai installé Windows 7 on an old laptop yesterday evening, so that I could experiment avec Win32 API programming. I started it updating about 5 hours ago. It téléchargé the mises à jour in 30 minutes or so, but as of right maintenant it is encore l'installation them, and seulement 58% complete.
Pourquoi this taking so long, and what puis-je do to hasten it?
The laptop is an HP Pavilion dv6701us, avec 2 GB of RAM, a 120 GB SATA hard disk, and a dual core Pentium D CPU, for what c'est worth.
Mise à jour (July 18 2015):
I've maintenant observed this behavior on every Windows 7 machine in my household, 32 and 64 bit alike. Il semble que almost invariant avec respect to RAM, CPU speed and number of cores, even SSD vs. HDD. All Windows 7 systems J'ai vu updating, take over 8 hours to installer ~200 mises à jour.
Is there anyone for whom Windows Mise à jour is *not* spectacularly lent?
Mise à jour (July 19 2015): ici is the link vers le compressed xprof fichier:
[https://drive.google.com/file/d/0B7EgLkt64WtaWWc5YTJicThLNFk/view?usp=sharing](https://drive.google.com/file/d/0B7EgLkt64WtaWWc5YTJicThLNFk/view?usp=sharing)
Mise à jour (September 14 2015):
I n'était pas entirely satisfied avec the answer below - can Microsoft really be shipping quelque chose that broken? - so I decided to have a go at it avec Sysinternals procmon. Ceci est what I see, over and over again, while Windows Mise à jour hangs and ne even start downloading stuff:
```
High Resolution Date & Time: 9/14/2015 8:24:12.9744097 PM
Event Class: Registry
Operation: RegOpenKey
Result: NAME NOT FOUND
Path: HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\WindowsUpdate
TID: 3376
Duration: 0.0000183
Desired Access: Query Value
```
That WindowsUpdate clé ne exist. Could be c'est supposed to be nonexistent; but I strongly suspect otherwise, seeing as it is accessed over and over and over again by the updater's service host processus, in a seemingly endless loop. The question in that case, though, would be: what entries/valeurs should it contain?
Google/Bing jusqu'à présent n'a pas turned up anything, but I'm going to keep looking on this.
Mise à jour 2 (September 14 2015):
J'ai essayé the hotfix from ici:
[https://support.microsoft.com/en-us/kb/2700567](https://support.microsoft.com/en-us/kb/2700567)
It claimed to fix some things, including quelque chose about the mise à jour service registration being manquant or corrupt(!). Bizarre. C'est un fresh Windows 7 SP1 installer.
... Cependant, Windows Mise à jour is encore just as slooooooooow as avant, chugging away at 50% of disponible CPU power while appearing for all the world to be stuck in an endless loop.
Je viens de ne understand this. Windows has 90% du desktop utilisateur base, it cannot possibly be this awful par défaut... I will keep investigating.
Pourquoi Windows 7 mise à jours take so long to installer?
Re: Pourquoi Windows 7 mise à jours take so long to installer?
Starting avec Windows Vista the Mises à jour come as difference fichiers. So during setup, Windows need to creates the real fichiers based sur le diffs. Ceci est CPU intensive and takes some time especially on really old CPUs like your Pentium D.
In your provided xperf fichier you have a high CPU usage from TrustedInstaller parce que it needs to créez un `pending.xml`. This means that the updated fichiers were in use and had to be updated during shutdown/boot which results in this dialog:
Ici the CPU is busy writing the XML data
```
wcp.dll!Windows::ServicingAPI::CCSITransaction::GeneratePendingTransactionContent
```
and writing data invers le registry
`wcp.dll!Windows::Rtl::SystemImplementation::CKey_IRtlKeyTearoff::CreateNewKey`.
But the bigger problème is that you try to installer 5 .Net Framework mises à jour:
Maintenant Windows is busy parce que the .Net optimizer service `mscorsvw.exe` runs to compile the updated .net fichiers into machine code to improve performances and reduce mémoire usage of .net applications.
Ceci est également very CPU extensive and your `Intel Atom CPU N270 @ 1.60GHz` is too lent.
[Microsoft provided a script to speed this up](https://devblogs.microsoft.com/dotnet/wondering-why-mscorsvw-exe-has-high-cpu-usage-you-can-speed-it-up/).
In your provided xperf fichier you have a high CPU usage from TrustedInstaller parce que it needs to créez un `pending.xml`. This means that the updated fichiers were in use and had to be updated during shutdown/boot which results in this dialog:
Ici the CPU is busy writing the XML data
```
wcp.dll!Windows::ServicingAPI::CCSITransaction::GeneratePendingTransactionContent
```
and writing data invers le registry
`wcp.dll!Windows::Rtl::SystemImplementation::CKey_IRtlKeyTearoff::CreateNewKey`.
But the bigger problème is that you try to installer 5 .Net Framework mises à jour:
Maintenant Windows is busy parce que the .Net optimizer service `mscorsvw.exe` runs to compile the updated .net fichiers into machine code to improve performances and reduce mémoire usage of .net applications.
Ceci est également very CPU extensive and your `Intel Atom CPU N270 @ 1.60GHz` is too lent.
[Microsoft provided a script to speed this up](https://devblogs.microsoft.com/dotnet/wondering-why-mscorsvw-exe-has-high-cpu-usage-you-can-speed-it-up/).