Author Topic: Windows Rollup(Oct,Nov) 7 Professional 64bit  (Read 6502 times)

0 Members and 1 Guest are viewing this topic.

Offline ChuckR

  • Newbie
  • *
  • Join Date: Nov 2016
  • Posts: 15
  • Karma: 0
    • View Profile
Re: Windows Rollup(Oct,Nov) 7 Professional 64bit
« Reply #15 on: December 01, 2016, 09:25:37 AM »
As mentioned, I tried 3197868 on 11/30/2016 and it Reverted.  I looked into the CBS Log and wow I found the following which only a small portion of these errors.
Session: 30558846_681764211 initialized by client WindowsUpdateAgent.
2016-11-29 12:21:25, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2016-11-29 12:21:25, Info                  CBS    Session: 30558846_681774212 initialized by client WindowsUpdateAgent.
2016-11-29 12:21:25, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]

Many Session items did seem to initialize.
Where would ALL these come from?
I can't believe they are included in KB3197868

Since I found them I re-ran Tweaking.com.
Have not tried KB3197868 since then.

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 7092
  • Location: UK
  • Karma: 106
    • View Profile
Re: Windows Rollup(Oct,Nov) 7 Professional 64bit
« Reply #16 on: December 01, 2016, 09:49:31 AM »
See what this trouble shooter comes with -

https://support.microsoft.com/en-us/kb/2714434

Offline ChuckR

  • Newbie
  • *
  • Join Date: Nov 2016
  • Posts: 15
  • Karma: 0
    • View Profile
Re: Windows Rollup(Oct,Nov) 7 Professional 64bit
« Reply #17 on: December 01, 2016, 10:43:40 AM »
It did fix 3 of 4 issues.  One fix had an error code of 0x80070490.  I will look into this when I have time.
Thanks again for the help.
Have a good day.

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 7092
  • Location: UK
  • Karma: 106
    • View Profile
Re: Windows Rollup(Oct,Nov) 7 Professional 64bit
« Reply #18 on: December 01, 2016, 10:54:03 AM »
That doesn't bode well as you've already run these fixes -

https://support.microsoft.com/en-gb/kb/958044