Woody Leonhard's no-bull news, tips and help for Windows, Office and more… Please disable your ad blocker – our (polite!) ads help keep AskWoody going!
Home icon Home icon Home icon Email icon RSS icon
  • Solution for the error 0x8000FFF in Windows 7

    Posted on September 12th, 2018 at 15:05 PKCano Comment on the AskWoody Lounge

    Thanks to two reports from an anonymous poster and @Pradeep-Dixit here, there is a solution for the Error 0x8000FFF.

    It seems that an old Servicing Stack Update (or the lack of) is to blame for the error 0x8000FFF users have been experiencing with Windows 7 and the update this month. Servicing Stack KB 3177467 (September 2016) is a prerequisite for KB 4457144 2018-09 Security Quality Monthly Rollup for Win7. It must be installed prior to the September Rollup.

    This Servicing Stack Update KB 3177467 can be downloaded from the MS Update Catalog for 32-bit of 64-bit Windows 7.

    If you are not familiar with manual download/install from the Catalog, you can download the update by clicking on the 32-bit or 64-bit links above. Save the download to a known location. Close any open programs then double click on the downloaded file, agree to install, and reboot the computer when asked. After rebooting, you should be able to install the September Rollup. (Waiting for the DEFCON number to be 3 or above, of course.)

    This SSU also applies to Server 2008 R2

    Information  ComputerWorld Woody on Windows.

  • Massive (and frustrating!) sync failures with WSUS

    Posted on September 12th, 2018 at 09:41 woody Comment on the AskWoody Lounge

    Source: @jamiethornton

    I’m seeing reports all over the web about failed sync on WSUS servers, trying to roll out this month’s patches.

    SoapException: Fault occurred InvalidCookie

    InvalidOperationException: Client found response content type of ”, but expected ‘text/xml’.

    WebException: The operation has timed out.

    The problems arose before this month’s round of security patches — see Günter Born’s report — but admins are seeing even more occurrences since Tuesday.

    Removing Office 2016 and resyncing doesn’t seem to work.

    Anybody out there figure out a way to fix it?