Delivered-To: daveyxm@virginmedia.com Received: by 10.50.96.198 with SMTP id du6csp142178igb; Thu, 10 Oct 2013 12:49:45 -0700 (PDT) X-Received: by 10.180.89.98 with SMTP id bn2mr9284933wib.42.1381434584855; Thu, 10 Oct 2013 12:49:44 -0700 (PDT) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id g10si6901007wie.2.1969.12.31.16.00.00; Thu, 10 Oct 2013 12:49:44 -0700 (PDT) Received-SPF: neutral (google.com: 195.171.43.25 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) client-ip=195.171.43.25; Authentication-Results: mx.google.com; spf=neutral (google.com: 195.171.43.25 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) smtp.mail=owner-rsgb_lf_group@blacksheep.org; dkim=fail header.i=@mx.aol.com Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1VULmi-0002bc-40 for rs_out_1@blacksheep.org; Thu, 10 Oct 2013 20:20:32 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1VULmh-0002bT-M9 for rsgb_lf_group@blacksheep.org; Thu, 10 Oct 2013 20:20:31 +0100 Received: from omr-m01.mx.aol.com ([64.12.143.75]) by relay1.thorcom.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1VULmc-0006J6-OY for rsgb_lf_group@blacksheep.org; Thu, 10 Oct 2013 20:20:30 +0100 Received: from mtaout-db01.r1000.mx.aol.com (mtaout-db01.r1000.mx.aol.com [172.29.51.193]) by omr-m01.mx.aol.com (Outbound Mail Relay) with ESMTP id 9F6B1700000AA for ; Thu, 10 Oct 2013 15:20:23 -0400 (EDT) Received: from White (95-91-237-85-dynip.superkabel.de [95.91.237.85]) by mtaout-db01.r1000.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id C86B6E000110 for ; Thu, 10 Oct 2013 15:20:20 -0400 (EDT) Message-ID: <41E0EF3191314A6490E5D0DBFBD1E5B4@White> From: "Markus Vester" To: Date: Thu, 10 Oct 2013 21:20:19 +0200 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 12.0.1606 X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1606 x-aol-global-disposition: G DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20121107; t=1381432823; bh=xN9+Hul+ClW6hjgSXDSSO6nYGlfkS09N2GyziTgpQNY=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=L6QnFFVnWi2/1723YFLX0ao6x14dT7dwOaZolhvL6NgTqWU+8VQ5CSZCseWaj8lTr epbV0jSOEGWJyZjpCIV6dMfvvwIGT9W4SAAB7Wzoy9fDDaRRMog7bShkc2MCe97Njd g1IFC6zh1DYrPTmtn8Lyz/qkSI99Et+eJGwrPUzo= x-aol-sid: 3039ac1d33c15256fdf43fcf X-AOL-IP: 95.91.237.85 X-Spam-Score: -0.2 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: sorry if this is off topic: When I came home Tuesday night I found my grabber-notebook very slow, with the fan going at full throttle. Task-manager showed an "svchost" instance hogging all of the CPU. A bit of Google search indicated that the Windows update service may be the culprit, which indeed turned out to be the case. I attempted a couple of published fixes without permanent success. In the end the only way to revert to normal operation seemed to be to disable updates alltogether, and reboot. [...] Content analysis details: (-0.2 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [64.12.143.75 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (markusvester[at]aol.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.2 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 HTML_MESSAGE BODY: HTML included in message 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: 138e3b341e0543401afa7e97ee054540 Subject: LF: OT: Failed Windows update hogs CPU Content-Type: multipart/alternative; boundary="----=_NextPart_000_0010_01CEC5FE.85C10E70" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.9 required=5.0 tests=HTML_30_40,HTML_MESSAGE, MISSING_OUTLOOK_NAME autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false Status: O X-Status: X-Keywords: X-UID: 640 Dies ist eine mehrteilige Nachricht im MIME-Format. ------=_NextPart_000_0010_01CEC5FE.85C10E70 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable sorry if this is off topic: When I came home Tuesday night I found my = grabber-notebook very slow, with the fan going at full throttle. = Task-manager showed an "svchost" instance hogging all of the CPU. A bit = of Google search indicated that the Windows update service may be the = culprit, which indeed turned out to be the case. I attempted a couple of = published fixes without permanent success. In the end the only way to = revert to normal operation seemed to be to disable updates alltogether, = and reboot.=20 Yesterday night, the very same thing happened to my "other" netbook = which is nowadays used for Op-8, WSPR, 74 kHz, transmitting, and emails. = Both machines have been running fine so far with WinXP (SP3), IE 6 = browsers, and all past updates. I am wondering whether anyone else in the group has suffered from this = recently, and perhaps found a cure allowing to re-enable Windows = updates. Best 73, Markus (DF6NM)=20 ------=_NextPart_000_0010_01CEC5FE.85C10E70 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
sorry if this is off topic: When I came = home Tuesday night I found my grabber-notebook very slow, with = the fan=20 going at full throttle. Task-manager showed an "svchost" instance = hogging=20 all of the CPU. A bit of Google search indicated that the = Windows=20 update service may be the culprit, which indeed turned out to = be the=20 case. I attempted a couple of published fixes without = permanent=20 success. In the end the only way to revert to normal operation = seemed to=20 be to disable updates alltogether, and reboot.
 
Yesterday night, the very same thing = happened to my=20 "other" netbook which is nowadays used for Op-8, WSPR, 74 kHz, = transmitting, and=20 emails. Both machines have been running fine so far with WinXP = (SP3), IE 6=20 browsers, and all past updates.
 
I am wondering whether anyone else in = the group has=20 suffered from this recently, and perhaps found a cure allowing = to=20 re-enable Windows updates.
 
Best 73,
Markus (DF6NM) 
 
------=_NextPart_000_0010_01CEC5FE.85C10E70--