فقط استلم التالي أنّ يكون ارتبطت إلى ال [سفشست] إصدارات أنّ أنا قد كتبت حوالي في الماض…

قد أطلق سيدة "مكروسوفت أمن استشاريّة (927891) - نقطة معيّنة ل [ويندووس] مركبة ([مس])" أنّ ليس حقّا مباشرة أمن اهتمام, غير أنّ واقعيّا عناوين اهتمامات أنّ أمكن منعت الناس من يحصل أمن حرجة أو أخرى تحديثات.

بما أنّ سابقا يذكر, يتضمّن هو سيدة [كب] 927891 - "أنت تستلم [أكّسّ فيولأيشن] خطأ والنظامة يمكن ظهرت أن يصبح [أونرسبونسف] عندما يحاول أنت أن يركّب تحديث من [ويندووس] تحديث أو من مكروسوفت تحديثيفيد ", والمراجعات حاليّة من المادة (8.0) "هذا نقطة معيّنة واحدة عنصر من نقطة معيّنة من جزئين أنّ يتضمّن [ويندووس] تحديث زبونة برمجيّة تحديث. سينشر هذا تحديثات كنت تلقائيّا يستعمل [ويندووس] تحديث في شهر ماي 2007 ويونيو - حزيران 2007."

ثانية, هذا تحديث واحدة من اثنان أنّ حاجة أن يكون طبّقت أن كلّيّا خاطبت الإصدار. الأخرى تحديث صيغة 3.0 من [ويندووس] تحديث زبونة برمجيّة, يتوفّر من سيدة [كب] 932494, "عندما يستعمل أنت تحديثات آليّة أن يمسح لتحديثات أو أن يطبّق تحديثات إلى تطبيقات أنّ يستعمل [ويندووس] مركبة, أنت تختبر إصدارات أنّ يتضمّن ال [سفشست.إكس] عملية“.

واحدة

…

سابقا (هنا و هنا), قد كتب أنا حول يعزل يشارك خدمات [س ثت] هم يركضون في هم خاصّة عملية, مع بؤرة خاصّة على [ويندووس] تحديث تحديثات آليّة خدمة ([وووسرف]) أنّ بشكل خاصّ يركض في ال [نتسفكس] [سفشست.إكس] مثال. أنجزت واحدة شيء أنّ يستطيع كنت أتمّت مرّة هذا أن يخفّض الأولوية من العملية [س ثت] عندما الخدمة يلتفّ فوق يستهلك 100% من ال [كبو], النظامة لا يصبح [أونرسبونسف].

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

…

Previously (Part 1: Introduction - What’s using my CPU?), I kicked off what I expect to be a multi-part series on determining what is causing excessive CPU consumption, outside of the normal “which process has the highest value in the CPU column in Task Manager”.

Before I get into things, a little bit of background may prove useful or mildly entertaining. Over on “Sysinternals Forums”, there were recently two similar problems that both involved excessive CPU utilization that was not attributable to a specific process. I became involved in both problems and attempted to use similar techniques to get additional information with the hopes of ultimately being able to pinpoint the problem. What may make this mildly entertaining is that in both cases, there was limited or no success in detetmining the cause of or solution to the problem. In the end, one problem was resolved by disabling the floppy disk controller, and the other problem appears to be as of yet unresolved. (In the latter case, the poster did admit that the system was experiencing hardware problems - the chipset fan was dying and there…

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…

Recently, I have been involved in attempting to diagnose problems with excessive CPU utilization. Often times, this type of thing is relatively easy to identify - at least as far as pointing the finger at the thing that is consuming CPU cycles. Task Manager can be used for this - simply sort the “CPU” column in descending order and note the process that is at the top of the list. One can use a similar technique with Process Explorer.

In the past (here and here), I’ve given examples that demonstrate various techniques that can be used to try to determine what a process is doing when it is consuming so much CPU. Sometimes, you can do something about it - if you have the debugging symbols, perhaps there is something in the stack of the thread or threads in the process that is consuming the CPU that will lead you to some setting, feature, or configuration piece that can be manipulated so as to avoid the problem. Or perhaps just knowing the module name is enough information to identify the problem software - a recently installed add-in / plug-in, or a new utility,…