At this point, installation of the updates begain, with CPU utilization hitting around 65% at 12:02, peaking a few times at 100% at 12:04 before dropping down to 75% at 12:05 and dropping about 10% a minute after that until 12:08, when installation finished. I began the install of updates at 11:56 PM with CPU utilization at about 45% until updates finished downloading at 11:59. ![]() I first let ESET Smart Security 7.0.302.26 download all of its updates, and waited for it to finish and the system begin to idle (3% CPU) before starting Windows Update. Okay, the X220 I have has not been turned on for several weeks, so it has 36 updates (approximately 1,080MB) to install. Had to crash Windows again and reboot to uninstall NOD32 so at least I could work. Crashed out of Windows and rebooted and run log collector straight away before it got out of hand again. Computer was so slow the log collector would not run. ![]() I reinstalled today and it ran fine for two hours then all of a sudden, the fan started racing and the CPU usage went to 53% all attributed to NOD32. Problems have only started in last three days and 3-4 weeks after I upgraded to Windows 8.1 update so problem must be related to another program/service or the recent patches. Just to confirm, are you talking about the specific act of upgrading Windows 8 圆4 to Windows 8.1 (or Windows 8.1 to Windows 8.1 Update), or the monthly installation of Windows Updates (so-called "Patch Tuesday" updates)?Īlso, are you running Windows 8, Windows 8 Pro, Windows 8 Enterprise or some other version?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |