MS-DEFCON 3: Cautiously update Windows and Office

Topic

New Reply

It’s been a difficult month for Windows patches. If you’ve been following along here you know about: Odd Windows driver updates, distributed through Windows Update.

jmwoods has a great tip about renaming the Softwaredistribution folder:

Open an elevated Command prompt (Run as Administrator)…

1. Type: “cd %windir%” (no quotes for everything) and press enter.

2. Type: “net stop wuauserv” and press enter.

3. Type: “ren softwaredistribution softwaredistribution.old” and press enter.

4. Type: “net start wuauserv” and press enter.

Close the Command prompt window and try updating again.

Note: If you are trying to update logged in as a Standard user, and all users don’t have permissions to update, then you will need to be logged in as an Administrator.

[See the full post at: MS-DEFCON 3: Cautiously update Windows and Office]

Reply | Quote

Replies

I’m in Win7 Group B and when I check for updates I find KB3205402, KB3207752 and KB890830 waiting to be downloaded and installed.
So, which, if any, do I download?

Reply | Quote

KB3205402 is the .NET patch. Install it.

KB3207752 is the Monthly Rollup. If you’re in Group B, don’t install it. That’s the Group A patch.

KB890830 is the Malicious Software Removal Tool. Others disagree, but I say run it.

Reply | Quote

Please be very careful with the Windows 10 patch or patches for this month. Delivery Optimization still does not work well, Express packages still have chances to get stuck at 45% typically but can be another number like 1% or 99%.
To avoid any issues and because the patch including the hotfix to the patch is a good one, my recommendation is to go to the catalog with your favourite browser and download KB3213522 and install manually. This is only for 1607 which should already be installed on everyone’s Windows 10 machine.
At the end of the process, you should see only 3 patches under Programs and featuresInstalled Updates:

– KB3213522 (or KB3206632 – same patch without the hotfix, the only one on Windows Update, good enough, if you have this one there is no urgent need to install the hotfix on top of it)
– KB3199986
– Security Update for Adobe Flash Player

Reply | Quote

is there any problems with Win 10 1511 patchs? bugs etc

Reply | Quote

I haven’t heard of any.

Reply | Quote

YES! now u made my day

Reply | Quote

Woody,

Do you know of any way to get updates to find, d/l, and install faster? We have W7 Pro here at the office and I’ve been trying to d/l and install updates for days. Days. It took several days before it would even find the Patch Tuesday updates (that’s how long I’ve been fighting this), and once it did, I let the system run for four days over Xmas weekend and the d/l percentage was still at 0% when I came back on Tuesday. I’ve been trying all week to get them to d/l, and nothing.

I searched online to find a solution, and earlier this month found this from you:

http://www.infoworld.com/article/3105605/microsoft-windows/2-easy-steps-to-speed-up-windows-7-update-scans.html

I did everything it said. It didn’t help. Is there anything else that might help, or do I just wait? Thanks!!!!

Reply | Quote

thank you Woody,
just did the dec patch routine on win 7 32 bit woffice 2010
5 Office Patches:
KB3128037 excel
KB2889841 office security
KB3118380 office security
KB3114395 Microsoft publisher
KB3128034 word
4 Windows Patches:
KB3205402 security and quality rollup for (.drag)Net
trick bag KB3207752 which I promptly unchecked and hid.
and last but not least my defanged (de-heartbeated) Dec MSRT.
start to finish including mscoresvc’s run 1 hr. and six minutes. Now reset back to Never Check land, sweet dreams of days long go, when windows was FUN!

Reply | Quote

@Woody,

Is there any explanation as to why there is only a Security Only Update for .NET 4.6.2 and no Security Only .NET Update for versions below 4.6.2?

Is there ANY concern that the Security and Quality Rollup for .NET versions below 4.6.2 includes items that we don’t want on our machines?

Is there anyone here that has broken down the .NET Security and Quality Rollup to see what patches/updates are included (CanadienTech et al)?

I’m Group C but I have installed the previous .NET Security Only Updates. I WANT to install December’s .NET Security Update, but I don’t want any Rollups…so, I am really, really, reluctant to install December, 2016 Security AND Quality Rollup for .NET

I’m sure I’m not the only one dealing with this issue. Any thoughts will be appreciated.

Reply | Quote

Thank you for the go ahead on that .NET patch. I was hoping to hear what to do about it.

Reply | Quote

@Woody:

Question about the December Monthly Security ONLY update shown referenced for DL from the Catalog (KB3205394).
********************************

Once it is downloaded, is it then necessary to go to “Windows update service”, and stop it, or is this no longer necessary? I think I asked this once before, however did not see a reply by anyone.

*************************************

You did outstanding work, as usual, Woody. Thank you for all of your help!

Reply | Quote

@Woody:

P.S.

The update referenced (KB3205394)is a “stand-lone” update is it not, that you download to the desktop. Correct?

And it’s supposed to be installed from there. It’s been so long since I did one of these, I can’t recall.

Thank you once again.

Reply | Quote

Woody has asked me to post the following and I am doing so despite my reservations, which I won’t go into, but they have nothing to do with the substance of that which follows.

I have written a number of e-mails directly to Woody about the Realtek 2.0 Card Reader Driver matter. I am now posting parts of two on this board, in this thread, per Woody’s request. The first is somewhat redundant of what I posted last night on the Realtek thread but I want to establish context within this new thread.

1) I followed the suggestion of one of the members of the board to go into device manager and update the USB 2.0 Card Reader driver there. I did so, and, following installation, it gave me (automatically installed without asking if this is what I wanted) version number 10.0.10586.31225, not an updated version of a 6.0.xxxx, as I had expected. It also gave me non-functioning USB ports, all of them (unable to read message). The good news, if you can call it that, is that going back into device manager, and using the roll-back to the previous version option, for the USB card reader driver, restored functionality immediately without a need to reboot.

I know this is just one computer, so I write this with caution, but it could be very possible that MSWU, and updating via device manager, are telling machines with non Win 10 OS’s to install/update to Win10 drivers. FP’s experience with Win 8.1 (phone), and OneDrive, certainly falls into this category as well. For this reason, I can no longer trust what MS is telling me now pertaining to drivers for Win 7.

2) Go to MS Update Catalog (MSUDC) for the Realtek USB 2.0 Card Reader: http://www.catalog.update.microsoft.com/Search.aspx?q=realtek+card+reader . There are thirteen pages. Unless I missed something***, up until the very bottom of page 12, and then the top of page 13, Realtek driver 10.0.10586.31225 is designated as only a Win10 or above driver, see also this page: http://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=be553545-c567-45ff-a631-bd0cdf810b61 . When MSUDC talks about Win 7, before the last entry on page 12, it is the 6.XXXX series, pages ten and eleven (Mes..7777.. was right in his post).

But then there’s the bottom of page 12 and the top of page 13. Look at how unclear those two entries are: “Realtek Semiconduct Corp. – USB – 5/17/2016 12:00:00 AM – 10.0.10586.31225”, and this driver is numbered 10.0.10586.31225 and approved for Win 7, 8.1 and 8. There is no mention, like the other entries in the catalog, that this is for USB 2.0, it just says “Realtek Semiconduct Corp. – USB”. I think this is the origin of the problem and maybe this is what Dell picked-up on when it indicated the 10.0.10586.31225 driver is for Win 7, etc. as well as Win 10.

In the back of my mind last night, I was wondering if the conversions involved in the MSUDC was at the root of my Realtek problem. This research suggests it very well may be. It also seems to me that, regrettably, with every driver update one is going to have to dig into the catalog to confirm before installing. That’s a real drag. You guys have taught me how to do this, I am eternally grateful for this. But most people will never do this, or be able to do this, and they are just going to hit install when they see an available update in WU. May the force be with them.

Finally, I understand what I am about to write is not definitive but: If I see a driver being pushed to me by WU, for either of my two Win 7 computers, or my Win 8.1 tablet, and the driver starts with 10.XXXX, I am going to immediately be suspicious.

*** I rechecked the thirteen pages of catalog, both by looking and by a word search for “Windows 7”. On the first nine pages, there is no mention of Win 7. Then, on pages ten and eleven there is mention of Win 7 but the driver is a 6.XXX generation, just as Mes…777… stated previously. Then, on pages 12 and 13 there are the funky entries I wrote to Woody about in the first post above.

I cannot definitively resolve why Dell said the 10.0.10586.31225 Realtek driver is suitable for Win 8, 8.1 and 7, but, again, it does conflict with this http://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=be553545-c567-45ff-a631-bd0cdf810b61. I can report what I found in the catalog. I can report 10.0.10586.31225 disabled all my USB ports. I can report rolling back, via device mgr., to the 6.XXX generation driver immediately restored functionality.

Reply | Quote

Sooo we shouldn’t install the December Monthly Rollup update KB3207752 or is it safe to install the december monthly rollup?

What updates should I avoid when installing december updates?

Reply | Quote

Anyway I’ll wait until tuesday night jan 3rd to update. I’ll keep an eye out on the instructions on monday.

Reply | Quote

A patch for Office 2003 ? That’s a Christmas present for me ! I’m the only one left using Office 2003 in my corner of the world, and anyway Office 2003 has been officially cut off support ages ago, so why that sudden empathy for luddites such as me ?

Despite all prodding and warnings about impending exploit doom, I’m quite happy with my decision not to “upgrade” when I see official Microsoft warnings such as this :

> Outlook for Windows crashes when trying to add Outlook.com account (that’s Outlook 2013 or 2016, so 13 years of “development” and “enhancements” since I bought my version — and Outlook.com is the Microsoft mail service which is supposed to be the best thing since sliced bread ; and did I mention that both products were made by Microsoft ?).

> Outlook stops working or folders are missing or renamed when using Outlook.com in Outlook 2016 (because, who would think of using Outlook with Outlook.com, right ?).

> Drag and drop emails and attachments in Outlook does not work. After the Windows 10 Anniversary update, you may not be able to drag and drop emails, tasks or attachments in all Outlook versions, such as 2010, 2013 or 2016. You might also experience this issue in Thunderbird (because, thoroughly thrashing our own software is immense fun, but that does not mean we shouldn’t try and wreak other people’s software, too).

> When you double-click on a file, Excel does not open (because, why would you want to open a file just by clicking on it ?).

> When opening spreadsheets, Excel 2016 stops responding after installing KB XXX (because, only old farts would try to use Excel to open spreadhseets ; we’ve since moved on).

> In Word, right-click access to Auto-correct options is no longer available after upgrading to Office 2016 (yeah, that’s not a spoof or a hoax : it’s official Microsoft-speak that “upgrading” actually degrades your software).

Just a small selection of the problems I don’t have by the virtue of sticking to Office 2003 and Windows 7…

Reply | Quote

With all due respect to Woody and the AskWoody.com website, there has been a tremendous amount of FUD generated here on these driver updates, and updates in general.

It’s pretty simple…if your system is running OK, you don’t NEED to install any driver update.

Hide them, and move on.

I do it in a test environment to see if there are any side effects.

Additionally, the updates are marked “Optional”, so that is another clue.

Windows 10 users can run “wushowhide”…

https://www.tenforums.com/tutorials/8280-windows-updates-hide-show-windows-10-a.html

Wait a while (I have done it as part of my “month-end” maintenance for years) to install updates (now rollups and security-only updates), and do a full disk image before.

Never experienced an issue with this approach.

Not patching opens you up to more serious problems, such as malware, and now, ransomware.

You do have control of your systems.

Reply | Quote

Just to be clear on Win7…

Ignore both optional Intel updates correct?
INTEL – System – 10/3/2016 12:00:00 AM – 10.1.1.38
and
Intel – System – 3/13/2016 12:00:00 AM – 11.0.0.1010

thanks!

Reply | Quote

Yes. Do NOT install any Optional patches, especially drivers. That’s true for both Group A and Group B. (And Group W, come to think of it.)

Reply | Quote

That’s a variant on the Group A approach where, instead of waiting until the end of the month as you do, folks wait until I give the all-clear (which varies from the third week to early the following month, depending on what problems I see).

Most folks don’t have a test environment. My Great Aunt Martha would be flummoxed if I told her to take a full disk image.

I guess FUD is in the eyes of the beholder.

Reply | Quote

If you’re in Group A, install the Monthly Rollup, the .NET patch, and any Office patches.

If you’re in Group B, follow the instructions to download and manually install the Security Only update, then install the .NET patch, and any Office patches.

Reply | Quote

Excellent analysis. Thank you!

Reply | Quote

If you’re in Group B, follow the instructions to download and install the patch.

Reply | Quote

No need to stop the Windows Update service. Follow the instructions here:

http://www.infoworld.com/article/3136173/microsoft-windows/how-to-cautiously-update-windows-7-and-81-machines.html

Reply | Quote

Sure. It’s exactly as Abbodi described – the “security only” .NET patch this month is all smoke and mirrors. “Both .NET 4.6.2 updates [the Security-only and Security Rollup] are identical it seems they created the security-only update just to comfort the non-security haters. Apparently they didn’t feel the same or have the time to do that with other .NET versions.”

Reply | Quote

Does this work?

http://www.infoworld.com/article/3136677/microsoft-windows/how-to-speed-up-windows-7-update-scans-forever.html

If not, the gold standard is at wu.krelay.de/en

Reply | Quote

I always hide the Optional patches. I only install the important updates except when I gotta hide the ones to not install.

Reply | Quote

For Group B Woody can you explain which updates to install.

now the security only update is kb3205394 to install manually right?

And when you check for updates install the .net patch and any office patches right?

Reply | Quote

Right. I have the links to the 32-bit and 64-bit versions of the Security-only update in the blog post.

Follow the instructions here

http://www.infoworld.com/article/3136173/microsoft-windows/how-to-cautiously-update-windows-7-and-81-machines.html

As noted in Step 7, make sure you get the .NET patch and the Office patches.

Reply | Quote

@Woody:

Is there a “deadline” for DL & installing the
Win Updates, as well as the December 2016 SECURITY ONLY download from the Catalog?
*************************

Group B
Win7 x64

Just don’t want to get left behind insofar as getting these updates installed BEFORE any “deadline”.

Thanks for your advice – – – I think a few others may have wondered about time restrictions as well. ??

Reply | Quote

Just a little heads up – don’t know if anyone else had this – I’m running W7 x64 on a desktop and laptop – the .NET patch (kb3205402) hung at halfway for ages (a good 5 – 10 minutes) when ‘Installing Updates…’ Green bar went static etc. It did clear eventually, but I was on the verge of stopping it.

Reply | Quote

Realize that we’ve only been doing this for three months but, no, there should be no expiration date for the Security-only patches.

Reply | Quote

WSUS for the office.

Reply | Quote

Thank you, Woody!

Reply | Quote

See https://blogs.msdn.microsoft.com/dotnet/2016/12/13/net-framework-december-monthly-rollup-is-now-available/

Reply | Quote

@Woody:

You have written above:

Right. I have the links to the 32-bit and 64-bit versions of the Security-only update in the blog post.
***********************************

Is the BLOG POST you reference the one Dated October 27, 2016?

I keep seeing references to “BLOG POST”, but I’m not quite certain that this is what it is??

Thank you for any clarification you may be able to provide, since it references “LINKS”, and this post is from October 27th. ????

Reply | Quote

Most folks don’t need a test environment.

I would argue that people such as your Great Aunt Martha can learn to do a full disk image.

You could set it up for her.

I think banging the drum for frequent disk images is more productive than the “Oh My God, what has Microft done now” slant that seems to run through the topics here.

I appreciate what you’re doing and the service you offer, but a lot of the hysteria, and the FUD it creates, is counter-productive IMO.

Reply | Quote

I’d like to add a little more detail from my own experience about 3 hours ago, also running W7 x64 (Group B):

It took a total of 14 minutes – from start to finish – to download and install the 7 Important updates [5 Office 2010 and 2 W7 (.Net and MSRT)].

Indeed, the .Net patch was taking a long time to install; however, in my experience, .Net updates/patches usually take a lot longer to install than most other updates.

Reply | Quote

This is something recurring monthly, not a patch as such. I am not getting into details because this product is no longer supported.

Reply | Quote

“I guess FUD is in the eyes of the beholder.”

It depends on the degree of technical ability and the degree of tolerance to risk too.

Reply | Quote

Yes. Do NOT install any Optional patches, especially drivers.

+1

Reply | Quote

Okay :3 Thank you for making it clear. I’ll do the updates next week. I’ll install them tuesday night on Jan 3rd.

Right now I gotta relax-been very busy during this week. Lots of books to sort at the library, after christmas sales and also helping my mom out-She just had knee surgery yesterday and I’m helping her during her recovery process and I have books to read and writing a poem to put in a co-worker’s memory book because she is retiring from the library tomorrow and her retirement party is next friday.

Anyway thanks for saying about I having it right: Manually install the security patch when windows update is off, then turn on windows update, scan and install the .net and office patches, hide the optional patches and any unnecessary updates hidden in important.

Easy to follow, easy to understand. Also luckily my laptop doesn’t have an intel driver for any conflictions so it’s good.

Reply | Quote

“Windows 10 and later”.? = Win 11.?
……. This term will be quite confusing after March 2017 when M$ end support for Win 10 Version 1507 or RTM Build 10240.

Reply | Quote

+1

Reply | Quote

Presumably you installed the October update in October or November.

This blog has links for the December Security-only update.

Reply | Quote

Huh?

Reply | Quote

@ oxb ……. Fyi, the new monthly Patch Rollup for Win 7/8.1 from Oct 2016 onward are cumulative, similar to Win 10. Hence, KB3205402 is a huge 133MB file(64bit) = takes longer to download n install.
……. There hv been reports that the Dec 2016 cumulative update for Win 10(= nearly 1GB in size/64bit) took hours to complete. So, soon updates for Win 7/8.1 will take as long or even longer to install/complete as the monthly Patch Rollup accumulate, eg in July 2017.
.
“Rolling stones gather no moss”.?
“Rolling updates gather a lot of Mo$$”.

Reply | Quote

@ oxb ……. Also, for Win 10 Version 1703(= Creation Update) in March 2017, M$ will improve its update with Differential Updating, ie non-cumulative update, which was exactly what Win 7/8.1 were using b4 Oct 2016.
……. So, after March 2017, M$ will make updating for Win 7/8.1 worse/longer, while making updating for Win 10 better/shorter. Wonder why.?

Reply | Quote

@ jmwoods ……. Making frequent disk/system images cost quite a bundle of money, eg gotta buy an external USB hard drive/1TB which costs about US$70. Not everyone is “rich” like yrself.
……. The much cheaper back-up/recovery alternative is to create a Win 7/8.1/10 Install/Recovery DVD+R which costs about US$0.70.
……. The cheapest n free alternative is Askwoody.

Reply | Quote

@b
I see Security Update for Word Viewer in WSUS under updates for Office 2003 every month.
I don’t know what that means because I don’t follow Office 2003. In December 2016 I see 3 times same Security Update for Word Viewer as KB3127995, KB3128042, KB3128044.
They may be reissued patches or common patches with newer products, but they are available as I said every month for Office 2003, beyond the official end of support.

Reply | Quote

Sorry, the correct numbers are:
KB3127995
KB3128043 this is the correct number
KB3128044

Check those examples in the Catalog if you don’t have WSUS and you will understand what I said.

Reply | Quote

This site features posters who run the gamut from “Martha” to very high-level expertise. I sense no hysteria, but a good measure of hysteria prevention/relief.

One common desire for most who visit/contribute is that their computer systems (and related investments) operate properly, whether 1 or 150. As long as I’ve lurked/posted, that was always the underlying theme. GWX (and the MS-induced FUD) virtually forced a change in course. All of a sudden, there were a whole lot of folks playing defense. AW was pro-active in its reaction. At the height of the GWX storm, this place was the daily barometer.

It’s carried on with issues (and answers) presently with Win 10. Lots of rookies asking good questions and often getting solutions. Often within one day. Right here. That’s productive. As MS continues to evolve (flounder?) with its OS, I think it’s resonable that many have taken a defensive stance and tone.

There can be no question that thousands of people who never have posted here have gleaned valuable information simply by reading and gaining solid information. Woody needs a counter on the upcoming Lounge front page.

This issue of timely backups has been covered repeatedly. No doubt that it is relief for Excedrin Headache #1. When was the last check of that spare tire?

@Woody … you can make no flounder jokes at my expense.

Reply | Quote

thanks again!

Reply | Quote

https://catalog.update.microsoft.com/v7/site/Search.aspx?q=office+2003

Sort by Last Updated and let me know if you can make sense of it.

Reply | Quote

With Office2013 issues last week, I did a full disk image – with all my data on a NAS, it still took 300+gb, which was a fair chunk of one ext. hard drive.
If you had great photo albums and catalogues of music/iTunes, it could be quite huge and take a fairly long time.
Your patience with all these queries today is to be commended, Woody! Here’s hoping this system gets better, quickly (ok, I should go take my tablets now, try to get rid of the delusions, hey).

Reply | Quote

https://www.youtube.com/watch?v=u2c9-LDP0t0

Reply | Quote

See ch100’s screenshot here.

Reply | Quote

$70 is cheap compared to what ransomware hackers charge to decrypt your files…if your files are decrypted at all by the private key the sell.

An oil change on your car every 3 months for a year would cost you over $70…

You probably spend more than $70 a month on beer and cigarettes…

Don’t need to be “rich”.

Get over yourself.

Reply | Quote

https://s-media-cache-ak0.pinimg.com/564x/64/0d/07/640d07415163503480f47ac2bf8592e6.jpg

Reply | Quote

I already installed the optional intel driver and can’t see a way to roll that back easily. Suggestions, please?

Reply | Quote

https://www.microsoft.com/en-us/download/details.aspx?id=4

View, print and copy Word documents, even if you don’t have Word installed. This download is a replacement for Word Viewer 2003 and all previous Word Viewer versions. NOTE: The Microsoft Word Viewer is being retired in November, 2017. At that time, the Viewer will no longer be available for download and will no longer receive security updates. See Details for more information.

https://support.microsoft.com/en-us/kb/891090
How to obtain the latest Word Viewer

It looks like the Word Viewer 2003 gets all the equivalent updates for Word, any version. However the patches for Word Viewer 2003 are released under a different KB number.

Is Word Viewer 2003 such a dangerous old piece of software to get regular security updates far beyond its declared end of life?

Reply | Quote

Every day that passes adds more justification to group W. That’s the non-masochist group.

Reply | Quote

Windows 7 64 bit Group B
Updated the Security Only Update via Woody’s link.
Lost all my restore points. (and I had several prior to this update)
crossing fingers…..

Reply | Quote

I agree completely with your sentiments “Jim in Yakima”. Microsoft’s GWX campaign did incredible damage to Microsoft’s reputation. The GWX campaign also highlighted and drew attention to the great work and service Woody provides on convering Windows and MS Office.

Reply | Quote

I think that’s precisely the situation. Microsoft doesn’t want to continue supporting a product that’s duplicated by the Office Online apps.

Reply | Quote

Woody, not that I would ever install one but I noticed on the page I use to get updates (in Group B) that there is no Preview of monthly updates this month like there was the previous two months. Just found it interesting. I though MS was supposed to do that every month.

https://support.microsoft.com/en-us/help/22801/windows-7-and-windows-server-2008-r2-update-history

Updates for Windows 7 SP1 and Windows Server 2008 R2 SP1

Show all

December 13, 2016—KB3207752 (Monthly Rollup)
December 13, 2016—KB3205394 (Security-only update)
November 15, 2016—KB3197869 (Preview of Monthly Rollup)
November 8, 2016—KB3197867 (Security-only update)
November 8, 2016—KB3197868 (Monthly Rollup)
October 18, 2016—KB3192403 (Preview of Monthly Rollup)
October 11, 2016 — KB 3192391 (Security only update)
October 11, 2016 — KB 3185330 (Monthly rollup)
September 20, 2016 — KB3185278
August 16, 2016 — KB3179573
July 21, 2016 — KB3172605

Reply | Quote

Post coming up in the main area shortly.

Reply | Quote

Hello Woody,
I have not received any Microsoft update notifications in it seems like months. When I look at the update page through the CONTROL PANEL it says I am up to date (that is without running the manual update). I have Windows 7 SP1 with IE 11. Is there a reason there are no updates? Is everyone having the same issue?
My update options are
Download updates but let me choose to install them
Give me recommended updates the same way I receive important updates. (UNCHECKED)

Thank you,
Tom Spero

Reply | Quote

@jmwoods

It may come as a surprise to you, but some people actually cannot afford what you can afford. Berating them for that has become accepted behaviour on “the Internet” (or whatever that is). It’s nevertheless beyond the pale.

Also, flawed logic (not to mention rotten arithmetics) : you spend x on y, therefore you can afford to spend another x on z.

Reply | Quote

@ jmwoods ……. It’s foolish to spend US$70(= disk/system images) when u can spend US$0.70(= a Windows Install DVD+R) for the same purpose, ie to recover from ransomware.
……. Fyi, unlike businesses n govt offices, most home users n Woody’s Great Aunt Martha, do not keep important or indispensable files in their cptrs.

Reply | Quote

For those who are concerned that there is no Security only patch for .Net Frameworks 3.5 or 4.52 the above blog post states “The December Security Only update is only applicable to the .NET Framework 4.6.2. The vulnerability that it addresses does not impact 4.5.2 or 3.5.”

Reply | Quote

Shoot. I screwed up and installed the Security Monthly Quality Rollup. Will a restore undo it?

>Most important: UNCHECK the box next to the Security Monthly Quality Rollup. If you install the Security Monthly Quality Rollup, it will propel you into Group A.

Reply | Quote

Thanks! This worked great on my grandson’s W10 laptop (which had a “stuck point” of 95%, btw.)

Reply | Quote

First try should be to simply uninstall it.

Reply | Quote

By choosing “download updates but let me choose to install them,” you’ve given Microsoft carte blanche to install any recommended or important updates when you restart your machine.

If you want to control updating on your machine, you should choose the “Never check” option, or “Notify but don’t download.”

Reply | Quote

Yep. Looks like Microsoft took a break this month on their usual 3rd Tuesday Previews. guess everybody’s out on vacation.

Reply | Quote

Woody, you are a genius. I didn’t have KB 3172605. Now I do, and ten minutes later, the updates are installing. Thank you, thank you, thank you!!!!

(I mailed in a contribution before. I’m going to mail in another.)

Reply | Quote

Not everyone at Microsoft is on vacation it seems.
Instead of the regular preview patches, there was a push for few drivers compatible at the same time with a range of Operating Systems, in general 7/8.1/10 and the equivalent server OS. In fact they were all older drivers made compatible and certified for Windows 10/Server 2016 and at the same time backwards compatible with older operating systems.
Because this was not documented and this is not unusual because Microsoft drivers have never been documented, some people and many of us here found it difficult to deal with the issue in an acceptable manner, at least for the first few few days. It all came by surprise beyond anything else.
If the common sense rules were followed, which means not to install Optional updates unless really needed and fully understanding the implications, there would not have been any issues.
Maybe this is the main lesson to be learnt for the future.

Reply | Quote

Okay, you guys. Those were good … you win!

Reply | Quote

@TSpero,

Try changing to “Never Check”, reboot and then do a manual search for updates. Make sure you have KB3172605 installed before you do the manual check. KB3172605 is the “speed up” patch so your machine doesn’t search for hours.

If you don’t have KB3172605 installed you can get it with a search of the MS catalogue.

http://www.catalog.update.microsoft.com/Search.aspx?q=KB3172605

Reply | Quote

Perhaps if you go to Administrative ToolsServices and disable the Diagnostic Tracking Service first, it will remove that too. That is MS’s snooping service on Win7/8.1

Reply | Quote

why should 1607 already be installed on everyone’s Windows 10 machine? as is can see sticking to 1511 was a smarter choice with 1607 being worse than a viruse to erry one who have it installed

Reply | Quote

No they won’t, it’s already differential, and Cumulative Model will stand still
the “upgrades” are the ones that will be differential

Reply | Quote

@Woody:

I see the links above in your main post.

It references “Stand alone”, etc. Just to be certain, does this mean that when the update appears, after I click on it, I leave the “open with” (Win update Stand alone installer (default). Then just click on OK?

As I mentioned it’s been so long since I did one of these I can’t recall.

My apologies once again.

Reply | Quote

There was a time I could work full time, had lots of money coming in, and could go buy this or that (never cigarettes and beer, though). Life circumstances changed, and I can no longer do that. Budgeting for me comes down to how much fresh fruit and veggies vs canned, and will that be enough to get me through the month. My laptop is a life-saver, giving me access to the world, especially on days that 10 feet outside my front door is too far away for me to travel. Through my laptop I can communicate with friends and family, create, and explore. The walls and limitations of my physical world fall away. I didn’t choose to look into tech… I have to, or I will lose what is left of my world. I want a back up, so when my OS or this laptop bites the dust, my days will not be empty. A budget, not having devastating update failures, what I learn here on AskWoody, keeps me going in a good way. It is the new “Window” on the world that has opened up for me, not just a tool to run a business, make money or convenience to social chit-chat. Woody, and the other contributers here- you have no idea how grateful I am to have found this site. The answering of the most basic questions allows me to move forward in new directions… protect my laptop… and gives real hope. It isn’t a level playing field out there. It astounds me when people with so much money (like Satya Nadella) are so clueless and callous… but not surprising. So much could be and is being done to use tech to connect not just normal users, but differently abled folk… The fact that Windows Update comes along and wipes out all the settings that lets a differently abled person utilize it in the first place is horrendous on an individual scale. Microsoft has all sorts of accessibility built in now-a-days… and then wipes out ability to access it through their profit only, data mining focus… They need to consider a new accessibility feature for people who have to have someone else configure and re-configure their “Window’s Experience” to make it usable in the first place. It isn’t just businesses that need stability. I’d prefer not to be seen as differently abled (and in person it can’t be hidden), but this issue is so very important… and the approach here, of making tech accessible, is invaluable… Thank you, thank you, all of you.

Reply | Quote

Yep, if you’re in Group B.

Reply | Quote

You have to work hard to keep 1607 off your 1511 machine. That’s the way MS intended updates to go.

Reply | Quote

“…most home users n Woody’s Great Aunt Martha, do not keep important or indispensable files in their cptrs.”

Are you sure?

https://www.bleepingcomputer.com/forums/t/606583/cerber-ransomware-support-and-help-topic-decrypt-my-files-htmltxtvbs/

Reply | Quote

Woody,
I don’t think you understood the question. I am not getting any update notifications. Is there a reason why? Is there just NO updates?

Reply | Quote

Louis,
I have not installed KB3172605. I have it hidden. I did this because of this post from Woddy “Microsoft yanks buggy speed-up patch KB 3161608, replaces it with KB 3172605 and 3172614”. It seemed like there was issues between Microsoft and Intel??? Has this been fixed?? Are others using this patch (KB3172605) without issues??

Reply | Quote

I need to post and say thank you, Woody. I support my elderly mother’s win7 laptop and really appreciate your guidance on these updates. I’ve kept her Group B, since in the past I never installed anything but Critical and some Important Updates and saw no reason to change now. Whatever happens next month, I’m sure I’ll get the best advice on handling it here. Thanks again!

Reply | Quote

Woody,
I have “Download updates but let me choose whether to install them” but when I go to shut down and the yellow exclamation point is in the SHUT DOWN box telling me I have updates waiting to be installed I go back to the list of updates and hide all that I don’t want installed, usually all but security updates. This stops Microsoft from having carte blanche to install updates. I can then go back at my leisure and go through the list at RESTORE HIDDEN UPDATES to see if I want to install any. I did this at the time because it was taking forever to manually check for updates if you had NEVER CHECK as the chosen option. I don’t know if this speed problem has been solved because I never installed KB3172605 after reading your “Microsoft yanks buggy speed-up patch KB 3161608, replaces it with KB 3172605 and 3172614” post and noting the problems you listed between Microsoft and Intel. I have not seen anything that has said that the problems with that update have been solved so I still have it hidden.
Anyway this is not the problem as I stated in my other reply. The problem, if there is one, is that I am not getting any notifications about updates.
Thank you,
Tom Spero

Reply | Quote

@jmwoods

“An oil change on your car every 3 months for a year would cost you over $70…”

Wow, it is extremely cheap over there.

Reply | Quote

The last Win 7 updates appeared on Patch Tuesday, Dec 13. You should be getting Windows Defender updates as well.

Reply | Quote

If you are not on 1607 when it is in CB+CBB+LTSB, then to me it looks like you are not actually updating. Or you are a business user who has other considerations to update and this is not the right forum to take advice.
You may have an argument that 1511 is more stable than 1607, but if you don’t follow the manufacturer’s instructions while under “warranty” then you don’t need to read my posts, because you know better than Microsoft and obviously in that case better than me.

Reply | Quote

Delivery Optimization is not working for the CUs.
They get stuck in certain conditions if using Express packages either using WUDO or BITS – Bypass option.
Manual installation using the full package always works.
It may be intended to have differential updates, however this is not always working as intended. Talking about 1607 only.

Reply | Quote

If you create your own custom procedure, then we expect you to tell us the results, not asking us why it is not working.

Reply | Quote

Yeah, that’s what i took away from the ham-fisted way they handled the .net updates this month. So, no .net rollup for me. Sorry, microsoft but you don’t get to take over my pc this month with whatever timebomb you got hidden in there*. Try again next month.

*not entirely serious

Reply | Quote

@Spero

I installed 2605, it solved the “check for updates forever” problem, however…having an older laptop I lost my Bluetooth. That’s the issue with 2605.

That said, I don’t use Bluetooth with this laptop so I’ve compromised by accepting the faster check for updates for the disabling of my Bluetooth. This is one of the reasons I opted for Group C: MS can’t be trusted.

Reply | Quote

Louis,
I am not following. What is Group C? I agree that Microsoft can not be trusted. Did you follow my question? I am not getting UPDATE NOTIFICATIONS at all and I do not know why. Have you any ideas?
Thank you,
Tom Spero

Reply | Quote

Thanks. Uninstall worked. I feared the install was an irreversible step intended to put one firmly in MS’s grasp.

Reply | Quote

It is if you do it yourself.

Reply | Quote

hey woody. happy holidays!

I think I still have the “Windows Update Cleanup” terabyte (TB) space bug with the KB3206632 cumulative update for Win10 v1607. I guess that issue is not fixed yet.

Reply | Quote

I have Windows 7 and recently installed Office 16. My Office 16 is on a volume license so the only way I can see to update it is if I want to automatically update Windows too. Up to this point, I’ve been trying to update Windows under the Group B plan.

So my question is: is it better to stick with Group B plan and let Office 16 receive no updates or bite the bullet and let Microsoft automatically update both? Thanks.

Reply | Quote

do u mean the microsoft that pushs Windows 10 driver updates to windows 7 pc’s dude ty for making it clear that i made the right choice since the manufacturer is destroying ppl pc’s using us as betta tester with updates and u say am not actually updating. tyvm and as for WIN 10 it killed more pc’s than viruses does, and ppl should sue them for that globaly not just in the USA

Reply | Quote

Am following ur guide with the wuhide tool

Reply | Quote

None of the above work for me. KB3172605 does the same as the Dec. security only checking for updates for this computer for 8 hours. No disc activity at all MS is the worst I have ever seen for support. Linux for me from now on NO scrapple as they are just as bad

Reply | Quote

What are you talking about?

Reply | Quote

I don’t understand.

Are you scanning for updates, or installing the Security-only patch?

If you’re scanning for updates, follow these instructions:

http://www.infoworld.com/article/3136677/microsoft-windows/how-to-speed-up-windows-7-update-scans-forever.html

In rare cases that won’t work, and you need to follow Canadian Tech’s solution here:

https://answers.microsoft.com/en-us/windows/forum/windows_7-update/windows-update-doesnt-work-even-with-the-solution/1e7c6642-fd2b-4122-a62d-b5dff90b777d

If you’re installing a downloaded Security-only patch, did you disconnect the internet prior to installing the patch?

Reply | Quote

That’s the way to do it.

Don’t worry about the naysayers too much. Up until a couple of months ago, I wasn’t willing to move to 1607 either.

http://www.infoworld.com/article/3136257/microsoft-windows/windows-10-anniversary-update-finally-ready-for-prime-time.html

Up until a month ago, Microsoft wasn’t willing to recommend 1607 to its business customers.

http://www.infoworld.com/article/3145396/microsoft-windows/microsoft-deems-windows-10-anniversary-update-enterprise-ready.html

Reply | Quote

You’re talking about Office 2016?

Updates for Office 2016 come in through Windows Update. Just follow the instructions – don’t install the Monthly Rollup – and you can update Office 2016 with no problems.

Reply | Quote

@ ch100 ……. Fyi, there r reports that some Win 10 Version 1511 users could not do the upgrade to Version 1607, eg the upgrade stuck at a certain % percentage n were then automatically rolled-back n buyers of very cheap OEM Win 10 netbooks that came with only 16GB or 32GB of eMMC Flash storage.

Reply | Quote

Yep, I’ve seen it too. Sigh.

Reply | Quote

Elly, no need to explain yourself. Woody is here to help all of us,regardless of ability. Unfortunately,some posters need to beat their chests and take others to task for not thinking their way. I tend to follow Woody’s lead and ignore the people that find fault. I hope things get better in the new year.

Reply | Quote

There are several other known reasons why 1511 machines didn’t upgrade to 1607.

Reply | Quote

@ ch100 ……. There hv been reports that some Win 10 Version 1511 users encountered problems upgrading to Version 1607 = hv to stay on Version 1511.

Reply | Quote

From @jmwoods (I hope I moved this properly):

The flawed logic is…

“The much cheaper back-up/recovery alternative is to create a Win 7/8.1/10 Install/Recovery DVD+R which costs about US$0.70.”

Does not recover your data.

Reply | Quote

@ jmwoods ……. The link u provided at bleepingcomputer talks about a ransomware victim trying to decrpyt files encrypted by the ransomware.
……. That is not the proper recovery method for ransomware n other malware infection. Like u said, the proper recovery method is the expensive creation of frequent disk/system images or like I said, the creation of a much cheaper Windows Install DVD+R(esp for home users).

Reply | Quote

@ woody ……. Fyi, u can also create a Windows disk/system image without any data backup, ie by putting system files on the /C drive n all data files on a separate /D drive during the install process, n then create a system image only for the /C drive.
……. Not everyone needs to backup their data, esp if they do not keep important or indispensable data files on their cptr, eg if there r, they can be stored/backed-up on a USB Flash-drive.

Reply | Quote

Does anyone know if there is any need (or benefit) for installing Office updates pertaining to components you don’t have installed? I only use Access, Excel, Powerpoint, and Word, so can I safely ignore security updates for Infopath, Outlook, etc?

Reply | Quote

That explains it then…

Reply | Quote

Thanks for the response. I think I might be a little confused by Microsoft’s description. To update Office 2016, I click on a link in Windows Update that says “get updates for other Microsoft products”. It then takes me to a page called Microsoft Update which is described as to offer updates for Windows, Office and other Microsoft products. Microsoft Update gives me two options to select from: 1) Use recommended settings (windows automatically checks for important or recommended updates and installs them) or 2) Install important updates only (automatically install important updates but not recommended updates).
So if I check option #2, wouldn’t it install important updates for both Office 2016 and Windows? Or is it really only updating Office 2016?
For my Windows Update setting, I am using never check for updates.

Reply | Quote

Simple, you don’t trust the company, don’t use their product, use a competitor product.
There is no obligation for anyone to use a Microsoft product.

Reply | Quote

I think this is about the Click to Run product which Microsoft sells at a discount to employees of companies, academic environments etc and this is why the OP says it is a Volume License.

Reply | Quote

I find it interesting that anyone was explaining themselves, since the exchange was with a single poster (messager7777777), who abitrarily mentioned $70.

People are currently paying hundreds and in some cases thousands of dollars to get their systems and data back…regardless of how the damage occurred.

By comparison, $70 is peanuts to protect your system and data from any kind of disaster.

The math is clear.

Reputable tech sites constantly remind people to do full disk images, so I’m not saying anything new.

If it instills some discomfort to hear that your data could be gone because you don’t have backups, maybe that’s a good thing.

But it’s your computer.

Best of luck to you.

Reply | Quote

Not fixed in KB3213522 either.

Reply | Quote

Thank you. Woody is a good role model, having done a wonderful job with all the different people who come here.

Reply | Quote

Ah, Click-to-Run is a different beast entirely. It’s updated independently of Windows Update. Never heard of it referred to as Office 16.

Reply | Quote

OIC.

Try this.

Click Start, Control Panel, System and Security, Windows Update. On the left, click Change Settings. If you want Windows Update to check for Office patches in addition to Windows patches, check the box marked “Give me updates for Microsoft products and check for new optional Microsoft software when I update Windows.” Click OK.

That doesn’t change your “Never check for updates” setting. Windows Update (which you just switched to “Microsoft Update”) will only scan for Office updates when you run it manually.

Reply | Quote

Nope. Take everything that’s offered. There are dependencies that may not be at all obvious to you.

Reply | Quote

Thanks for the clarification and all the help you provide here.

Reply | Quote

I probably should check my facts better

Anyway, this is my last post in 2016, 2017 comes a bit earlier here than in most other places.

Happy New Year to all readers!

Reply | Quote

i used to trust the company since i never used but MS os’s from 98 – xp – vista ” even that is better than windows 10 ” win 7 , the company failing and destroying pcs have nothing to do with trust u destroy our pc’s then say use a competitor product, thats BS Dude and i wont complete this discussion ur company destroyed 2 of my pc’s then u tell me use another man … as respect to Woody i wont tell u what i think of MS

Reply | Quote

And MS didn even bother to list which pc’s will be upgraded And which will notfrom 1511 to 1607, in egypt where i live we are making a legal case against Ms after 1000’s of pc have died dude to MS failing to be as great as they was destroying ppls work,life memorys

Reply | Quote

WU in Windows 10 seems to be a lost cause

Reply | Quote

Click to Run is retail/subscription based, it does not come as Volume licensing

later, Visio and Project got C2R volume license, but this only because of the confliction between C2R and MSI
https://support.microsoft.com/en-us/kb/3157564

Reply | Quote

Group A. Is it safe to install KB3207752. I read somewhere on these pages that it has been problematical. Cant now find the reference to it so am holding off till I know its ok.

Reply | Quote

@ jmwood ……. U said, …”I think banging the drum for frequent disk images is more productive than the “Oh My God, what has Microft done now” slant that seems to run through the topics here.”
.
.
That’s quite a flippant attitude about M$’s ineptitude n greed.
…….There hv been many reports about M$ bricking the cptrs of ignorant n dummy Win 7/8.1 users who took the free Win 10 upgrade at M$’s urgings n/or trickery via Windows Update(= like a malware). M$ had informed them that their Win 7/8.1 cptrs were compatible for the free upgrade n they could roll-back. Most of these victims of M$ did not know how to recover their Win 7/8.1.
……. One US online-business lady successfully sued M$ over this matter n got US$10,000 in compensation = M$’s implied liability.

Instead of sympathizing with the victims of M$, u blamed the victims for not making frequent disk/system images n exonerated M$’s “evil” behavior , … similar to some male chauvinists blaming rape victims for dressing sexily.

Reply | Quote

Yes. That’s the Monthly Rollup.

Reply | Quote

Heaven help us all.

Reply | Quote

You certainly have a valid complaint. Whether you can win a case in court – is the big question.

Reply | Quote

ch100 has a valid point. If you’ve been bitten by Windows, use something different! You can sue and vote with your pocketbook at the same time.

I, too, used to trust much of what Microsoft made, and at least a little bit of what the company said. But that was long ago.

Reply | Quote

u know the newspaper i work in as a caricature artist from 20 years use windows from ages, last october they bought MAC pc’s replacing all the windows 10 pc’s we use cause it couldn read the storing harddrivers after the update TO 1607, i have no clue if they i can win the case to be honest olso MS telling us to switch to another OS if we do not like failure ??? … ALL the laptops except for MAC have this dysfunctional win 10 system on ALL new pc’s laptops in the markets & ppl are scared of buying any laptop with WIN 10 sign on it now n thats global … and they are clearly screwing win 7 too as i c

Reply | Quote

Question: does the MS-DEFCON usualy includes 1511 or this page now monitor 1607 only?

Reply | Quote

Thank you woody

Reply | Quote

@ abbodi86 ……. According to this link, UUP or Differential Updating should be applying to both feature updates/upgrades and cumulative updates, starting with the Creator Update to Win 10 Version 1703 in March 2017 …
https://blogs.windows.com/windowsexperience/2016/11/03/introducing-unified-update-platform-uup/#U23e4tOvPzyI68QL.97
.
Excerpt … “We have also revamped how devices check for updates, making them more efficient. As we move to UUP, we are reducing the update data sent to client devices as well as the amount of processing we are doing on devices, this especially important for devices built on the Mobile OS. Using UUP, when your device checks for updates, the Windows Update service will evaluate which updates are needed by a given device. The Windows Update service then returns these updates to the device for download and install. Because more processing is being done by the service, this will lead to faster checks for update operations. It’s important to note that with UUP, nothing will look or behave differently on the surface, UUP is all underlying platform and service optimization that happens behind the scenes.”

Reply | Quote

If you an I say it, then it must be serious
Woody would say it anyway

Reply | Quote

+1

Reply | Quote

I’m not convinced UUP will make any noticeable difference on devices other than phones.

Reply | Quote

This month, it looks like 1511 is ready to go, too.

Reply | Quote

@Woody:

How does a user “uninstall” something which was installed in error?

Hope it’s not a protracted process and available to everyone? Hopefully I will never need to use it.

Thank you.

Reply | Quote

Woody, I’m concerned about the statement you made here: “Although there’s a problem with one of the pieces of one of the .NET patches, it appears to be limited to Windows 8.1 machines running SQL Server. I’d guess that very few of you fall into that category.”

I’m in Group B, and I have a Win 8.1 system with SQL Server 2008 and ASP.NET MVC 4 Runtime. Is it safe to install the Dec 2016 Security and Quality Rollup for .NET Framework (KB3205404)?

Also, will installing KB3205404 still keep me in Group B going forward?

Reply | Quote

If you’re in Group B, you don’t want the rollup. You want to download and install the Security-only patch. Follow the link in the article, or wait for my much-more-detailed article in InfoWorld on Monday.

See this KB article for the “known issues” with .NET Framework 4.5.2

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

Reply | Quote

Same way you uninstall any other Windows patch. ghacks has a good step-by-step here:

http://www.ghacks.net/2014/12/11/how-to-remove-installed-windows-updates-and-block-them-afterwards/

Reply | Quote

@Woody:

Thank you very much for this link, which is excellent in its directions, and graphics.

Your help as always is outstanding!! Thank you, and thank you again!!!

Reply | Quote

Going to do that tomorrow night. Manually download the security only patch and then turn on Windows update to install .net patch and windows defender update and office patches.

Gonna install the updates on new years day

Reply | Quote

I want to thank everyone for the comments. This is the first time I was attempting to update Office 2016. I guess because of the volume license, I couldn’t do it directly in an Office program such as Word. As stated before, there is a link in Windows Updates to “get updates for other Microsoft products”. Clicking on that link gives me the two options previously mentioned. And then there is an install button to click.
I was worried that clicking on the install button would automatically install updates for Windows as well as Office 2016. But it turns out that clicking on the install button took me back to the Windows Update page. The automatic updates did start, but I had time to go into settings and change it to check for updates and choose whether to install them.

Now my question is which Office updates get installed? Just the important updates or important and recommended updates? Thanks for all the help and Happy New Year!

Reply | Quote

@ woody ……. This link says otherwise …
http://arstechnica.com/information-technology/2016/11/windows-switching-to-differential-patching-in-the-creators-update/
.
When Win 10 was launched on 29 July 2015, M$ stated that they would release feature updates/upgrades or new Versions of Win 10 about 2 to 3 times a year. If u notice, the time gap between the release of new Versions of Win 10 has lengthened, ie RTM Version 1507 — 4 months — Version 1511 — 8 months — Version 1607.
……. Hence, the Dec 2016 cumulative update for Win 10 Version 1607 is a huge 900+MB(64bit) download. By using UUP or Differential Updating for Win 10 Version 1703(= Creators Update), the download size of cumulative updates can be kept to a manageable size n this will allow M$ more time b4 releasing the next Version, eg 1 year till the next Version 1803.

Reply | Quote

One last question before the new year, is it safe to install update KB2719033? I have it showing up as an important update. Thanks.

Reply | Quote

Happy New Year Woody,

I just did the Security Only (Group 2) updating process, which went smoothly.

Follows are my observations of what took place:

==================================================
This is for Dell Precision M6800 Mobile Workstation:

31-Dec-16 / Saturday (After Ask Woody of 29-Dec-16)
Duration of Update Process: 2:23 PM > 2:50 PM

Installed: (What the available choices were)

KB3205394 Security Update for Windows (Win7 x64)

KB3205402 Dec 2016 Security & Quality Rollup for .NET Framework 3.5.1, 4.5.2,4.6,4.6.1, 4.6.2 on Windows & Windows Server2008 R2 for x64

KB890830 Windows Malicious Software Removal Too x64 – December 2016

————————-

This is what shows on Installed Updates:

KB3205394 Security Update for Microsoft Windows 12/31/2016 (This is the same as I chose)

KB3210136 Update for Microsoft .NET Framework 4.6.1 12/31/2016 (This is a different KB number)

KB3210131 Update for Microsoft Windows 12/31/2016 (This is a different KB number and title)

Showing on Office Account:
Windows Office Updates: (for MS Office Professional 2013) “Automatically downloaded and installed. Version 15.0.4885.1001”

==================================================
This is for Dell OptiPlex 390:

31-Dec-16 / Saturday (After Ask Woody of 29-Dec-16)
Duration of Update Process: 3:26 PM > 4:10 PM

Installed: (What the available choices were)

KB3205394 Security Update for Windows (Win7 x64)

KB3205402 Dec 2016 Security & Quality Rollup for .NET Framework 3.5.1, 4.5.2,4.6,4.6.1, 4.6.2 on Windows & Windows Server2008 R2 for x64

KB890830 Windows Malicious Software Removal Too x64 – December 2016

————————-

This is what shows on Installed Updates:

KB3205394 Security Update for Microsoft Windows 12/31/2016 (This is the same as I chose)

KB3210136 Update for Microsoft .NET Framework 4.6.1 12/31/2016 (This is a different KB number)

KB3210131 Update for Microsoft Windows 12/31/2016 (This is a different KB number and title)

Showing on Office Account:
Windows Office Updates: (for Microsoft Office Professional 2010) Secunia PSI says all are programs are up to date.

=================================================

Everything looks OK at this point.

Thanks for everything you do for us.

Chip

Reply | Quote

@Woody:

Thank you for that great link!!!

Reply | Quote

Feature update = upgrade
there is nothing related to cumulative updates

your excerpt is about “devices built on the Mobile OS”, aka phones

notice the word build:
“A differential download package contains only the changes that have been made since the last time you updated your device, rather than a full build.”

and the upgrade from Windows to later Windows:
“PCs where users can expect their download size to decrease by approximately 35% when going from one major update of Windows to another.”

Reply | Quote

In my view, either you update or you don’t. Don’t update if any of the known problems affect you.

I will continue to wait at this time. Regarding driver updates, I never install any from Windows Update, “recommended” or not.

I also see no reason to install any .NET roll-up such as KB3205402. There is no security patch for 4.5.2 (which I have installed) and I have no need for “reliability” patches when my systems work fine with 4.5.2.

Reply | Quote

“Dependencies”?

I only install Word / Excel / PowerPoint / Access / Publisher in my virtual machines with Office installed. I do not install any “irrelevant” patches such as InfoPath and Outlook. And for the few situations they were launched I had not encountered any problems.

So I will continue to ignore those patches when I come around to patch them.

Reply | Quote

Good news right down the line!

Reply | Quote

Wow. KB2719033 is four years old. Yeah, sure, go ahead and install it.

Reply | Quote

sEE

https://www.askwoody.com/2016/the-windows-unified-update-platform-uup/

Reply | Quote

@Woody:

Is there a problem with

KB3205402 Dec 2016 Security & Quality Rollup for .NET Framework 3.5.1, 4.5.2,4.6,4.6.1, 4.6.2 on Windows & Windows Server2008 R2 for x64

??
*******************************

In the past these have always been considered to be “safe”. What is the current recommendation for this one??

Thank you for your help on this one.

Reply | Quote

@ abbodi86 & woody ……. U said, … “No they won’t, it’s already differential, and Cumulative Model will stand still the “upgrades” are the ones that will be differential.”
…. which is incorrect, according to the arstechnica link that I provided above.
.
.
The link I provided at windowsdotcom does not specifically exclude UUP or Differential Updating for cumulative updates in Win 10. It would be foolish for M$ not to use UUP for cumulative updates as well, n just use it for feature updates/upgrades.
……. Anyway, come March 2017’s Creators Update, we will see.
.
Win XP/Vista/7/8/8.1 hv been using Differential or Delta Updating all along = non-cumulative updates — – until it was stopped by M$ for Win 7/8.1 in Oct 2016 = changed to non-Differential cumulative monthly Patch Rollups.

In Differential Updating, M$’s servers hv to work more during the monthly Patch Tuesday, as explained in the link I provided above.
……. In Win 10’s cumulative updating n feature updating/upgrading, the clients’ cptrs hv to work more, ie lazy M$’s servers just dish out the same huge cumulative update or Version upgrade file downloads to all the Win 10 cptrs according to their Editions, n then let the clients’ cptrs sort out the downloaded files themselves as to which updates r needed to be installed.
.
So, non-Differential Updating with cumulative Patch Rollups(Win 7/8.1) or cumulative updates(Win 10) does not benefit the users, ie it only benefits M$ = save costs with lesser cptr-servers.

Reply | Quote

Please see the link to my earlier blog post. Ars Technica is right, but you have to read between the lines.

Reply | Quote

@messager7777777 Obviously, I have no reason to doubt you on this, and it is consistent with what ch100 is saying about MS trying to make drivers ubiquitous, but this is the language in MS’s catalog, and it is all over the place. So, unless MS changes thousands, maybe a hundred of thousand, entries in the catalog, come March 2017, there will be even more confusion than there exists presently. I know, what a surprise coming from MS.

Reply | Quote

Woody: Can’t get into manage subscriptions

(https://www.askwoody.com/comment-subscriptions/?sre=80e87186885f8037309d833b4d031c24&srk=6e06b3624abdea05b3febc74f49f336a)

only thing on page is;
” Manage subscriptions

You have requested to manage your subscriptions to the articles on AskWoody. Follow this link to access your personal page:
[manager_link]”

What am I doing wrong?

Reply | Quote

arstechnica link understand it the wrong way, same as you as it appears
it does not matter if you get one cumulative update or multiple updates, it’s still differential when using Windows Update

Reply | Quote

You actually think that Windows Update download the whole update package each time?
it’s not, it only download the changed/applicablle files and in delta generated method

Reply | Quote

Have you recently installed IIS or maybe some related functionality on the machine? That would explain why you didn’t receive this update until now and you are receiving it now.

Reply | Quote

Unless you are running a web server that uses Internet Information Services (IIS) it’s not necessary.

Reply | Quote

Alright, boys and girls, a happy new year to all. I am just going to report this and let Ch100 and Woody try to make sense of it, but Woody, I believe you should consider adding 10.1.1.38 to the proceed with caution list.

I ran WU on my Winbook TW802 tablet, Win 8.1 OS. For the benefit of Ch100, the chipset on this device is: Intel Atom CPU Z3735f @1.33 GHz. WU update told me I needed the questionable 10.1.1.38 driver set. Clicking on more info gave me the reassuring comment to the effect that this page isn’t working now, come back later.

I went into device manager and found the exiting graphics drive to be 10.18.10.4276. Clicking on update device mgr. told me I didn’t need an updated Graphics driver. That was pretty interesting.

Running Intel’s Driver Update tool told me I presently had driver 10.18.10.4276 (consistent with device manager, and that I needed driver 10.18.10.4425. And this is consistent with what Intel’s website is telling me for this chipset as well: https://downloadcenter.intel.com/product/85552/Intel-HD-Graphics-for-Intel-Atom-Processor-Z3700-Series.

So, Intel’s info is confirmed in two ways, and MS’s info is conflicting all over the place and one cannot confirm what WU is pushing on MSUD web site.

If one goes to the MS Update Catalog, one sees 10.1.1.38 is initially designated as INTEL – System – 10/3/2016 12:00:00 AM – 10.1.1.38 but as you start to scroll through the 40 pages for this update one can see it is an attempt to lump all kinds of Intel chipsets, USB drivers, and who knows what else, into one update, because the list contains 1000 entries and miraculously, this MS Swiss Army Knife of an update is only 58Kb in size while the Intel authorized update is 69.21 MB.

I have no reason to doubt what Ch100 says that MS is trying to unify things and maybe 10.1.1.38 will work for some. But unless and until these updates demonstrably work for all MS is going to be causing a lot of grief. Well, let me rephrase that: a lot MORE grief.

Reply | Quote

Shoot me email and tell me which email address is subscribed…

Reply | Quote

@ JNP ……. In March 2018, Win 10 Version 1511 and Version 1607 will also stop getting support from M$, but the LTS branch of these 2 Versions will still be supported until 2025.
……. Seems, M$ hv shot themselves in the foot bc of greed.

Reply | Quote

@JNP

Thank you for following up on my request.
I don’t know if 10.1.1.38 would work for Intel Atom CPU with which my only encounter was few years ago when I owned a Dell Mini netbook.
I tend to be in favour of what you suggest, i.e. recommending cautiously to install 10.1.1.38, but only by downloading and installing the Intel Utility, which can be done even if the same “driver” was installed previously from Windows Update. The Intel utility is the complete set and will tell if that version applies or not to the user’s CPU/Chipset – it is a Chipset driver after all, but there is close association between CPU and the Chipset on the motherboard.
Here is the download link and you can safely ignore the brief description, in fact it has the same scope or more compared to the version pushed by Microsoft which can be seen in the xml file associated with the download.
https://downloadcenter.intel.com/download/26330/Intel-Chipset-Device-Software-for-Intel-NUC

However, for those who do not want to go “the extra mile”, if the Chipset update is presented as Optional and there was no previous attempt to install it, it can be safely ignored.

If the Chipset update is presented as Recommended, this means that there is no valid installation found on the system and I would recommend the procedure above, i.e using the Intel downloaded utility with the same version instead.

Reply | Quote

@JNP And one more comment, which I made previously. I own an older HP laptop, still very functional with Intel 5 Series Chipset, for which there is no 10.1.1.38 support.
I found instead that the latest utility supporting that Chipset was version 9.2.0.30
https://downloadcenter.intel.com/download/20019/INF-Update-Utility-Primarily-for-Intel-6-5-4-3-900-Series-Chipsets?product=1145
which works perfectly on Windows 10.
6 Series Chipset (Sandy Bridge) is transitional but unlike what seems to be documented on Intel’s site and 6 Series being considered legacy, 10.1.1.38 works for 6 Series too.

Reply | Quote

@ abbodi86 & woody ……. Excerpts from winaerodotcom, dated 05 Nov 2016, …
.
“Microsoft started delta updates with Windows XP and continued to deliver them for Windows Vista, Windows 7 and Windows 8.1. However, when they switched to cumulative updates for Windows 10, the delta algorithm apparently got removed. Now Microsoft is claiming that they’ve added delta updates for cumulative updates too.

The new update system was activated along with the release of Windows 10 build 14959, the latest preview build of Windows 10 Creators Update. It is called Unified Update Platform (UUP).”

Reply | Quote

@ch100

Thanks, I understood nearly everything you wrote and, the part that I didn’t understand I fear I will never understand (we’ll call it the NUC option :)).

But, here’s the obvious thing, the people on this board, and others like it, have spent a lot of time these past two-three weeks trying to make sense of this, and I think we now have. But that leaves millions of MS users still in the dark. They will indiscriminately install a recommended, or optional KB, or driver, and then they may very well end-up with a computer that has lost some or all functionality or have a function they don’t want.

I don’t have the time right now to go deep into this, but we have to back this bus up and remember that Windows is first, and foremost, an OS. Win 98SE, Win XP, Win 7 were the most stable and successful versions of this, although I never personally had problems with Vista. What MS is doing now, among other things, is turning its chosen OS, Win 10, into an ever-changing science project that is an OS in name only. There exist significant problems for end-users, both business and personal, with this business model but, if you start to think about it, and play this out in your head, you can start to see how this is going to impact the manufactures of PCs and the supporting peripherals, and software for same, as well, and quite possibly software developers too.

MS is playing a very new game with its OS, its users and its suppliers of hardware and nobody, who is being impacted by this new game, is having a say about it whatsoever.

Reply | Quote

@JNP
In Catalog wording
Windows 10 and later = 1507 and later (unless superseded by the other category below)
Windows 10 Anniversary Update Server and later = Windows 10 1607, Windows Server 2016 (1607 as well) and later

Reply | Quote

Clueless says:
January 1, 2017 at 9:54 am

Woody: Can’t get into manage subscriptions

(https://www.askwoody.com/comment-subscriptions/?sre=80e87186885f8037309d833b4d031c24&srk=6e06b3624abdea05b3febc74f49f336a)

only thing on page is;
” Manage subscriptions

You have requested to manage your subscriptions to the articles on AskWoody. Follow this link to access your personal page:
[manager_link]”

What am I doing wrong?
Reply

woody says:
January 1, 2017 at 6:11 pm

Shoot me email and tell me which email address is subscribed…

Email address subscribed: 7b0cfe12(at)opayq.com

Thx Clueless

Reply | Quote

winaero is wrong too
the delta algorithm is not removed or changed in Windows 10, or with the new rollups ro 7/8.1

i stand still, UUP is for “upgrades” only

Reply | Quote

@ch100

You mentioned your laptop, mine is a Lenovo V570, Win7 OS, Intel Core i502430M cpu @2.40 GHz. This is the computer the Realtek USB driver MS pushed broke the USB ports until I rolled back.

MS tried to push me Version: 11.0.0.1010 (catalog: http://www.catalog.update.microsoft.com/Search.aspx?q=11.0.0.1010) which has some interesting entries when you do some clicking:

1. Driver Model: Intel(R) Watchdog Timer
2. Description: Intel System driver update released in March 2016 Architecture: AMD64 , X86.

Lenovo does not have this on its web page for updates for the V 570 and the Intel Update Tool does not give me anything other than updating my wireless adapter. Lenovo’s scanning tool was unhelpful.

I don’t know what to make of this, other than your comment about MS wanting to setup older OSs for updating to Win 10 or above. My intent is not to do so, this package: Version: 11.0.0.1010 is optional, but still very confusing and possible to damage especially as the catalog says this is coming from Lenovo but Lenovo knows nothing of this update.

Reply | Quote

I didn’t understand the NUC either until I did research.
https://en.wikipedia.org/wiki/Next_Unit_of_Computing
It appears to be a motherboard in tiny form package from Intel which is sold as kit, but for our purpose, the components are the same like on any other motherboard from the same equivalent generation from Intel and sold by Dell, Lenovo, HP, Asus, Acer or white box.
There is no other 10.1.1.38 Chipset Driver on the Intel site which is closer to most other motherboards and this is the reason that I gave that one as example in my post and Microsoft does not appear to have other drivers posted than what is in that package from Intel. In this case, Windows Update identifies the hardware as Intel generic and not the manufacturer of the computer.
What I found is that the 10.1.1.38 set of drivers does not cover few USB Controllers usually found on Intel Series 7 Chipset equipped motherboards, in which case the drivers which apply are the previous ones, 9.x.x. This would still keep Windows Update quiet. I don’t know if this is something not intended or if the NUC kits are equipped with different USB Controllers, which is more likely. I can easily modify the xml file to create my own custom “drivers” to cover the missing USB Controllers, but there is little point in doing so. As we already know there is no driver involved as such and this package only makes the description of the components more accurate and creates placeholders where otherwise it would appear as a missing driver.
Regardless, for most people, Optional means that they do not need to install unless they take full responsibility over the components installed and are prepared to rollback if the installation does not go according to plan.
I install routinely all older Optional components and some are very useful in certain environments like the Remote Desktop 8 components, but I don’t install the Preview Patches unless I have a particular reason to do research. This does not happen regularly as I don’t see a purpose. With the drivers I take extra caution and in the situation I am tempted to try to install the Intel downloaded drivers instead of the Microsoft ones, but I am prepared for this to fail and I don’t have a definitive opinion about the usefulness of this procedure other than a feeling that “newer must be better” or at least more future-proof. Being future-proof is the only reason for which I moved to Windows 10, because Windows 10 as is now is much worse than Windows 7. But it was the same with Windows 7 vs XP for a very long time even after SP1 was released and most people tend not to remember.

Reply | Quote

All your points about the difficulties created by Microsoft’s approach to end users and businesses are valid.
The only one which I agree partially only and I mentioned in my other post is that the previous Operating Systems were very good unlike what we see now with Windows 10.
Vista was notorious for being unreliable until about Service Pack 2, while Windows 7 was not so good in the early days. I remember frequent mouse and screen freezes on Windows 7 which may have been due to faulty drivers but this is less important for end users.

Reply | Quote

I have a warning for 2 updates that caused a weird bootup glitch on a clients rig I just built.

KB3205394
KB3207752

They would randomly cause the machine not to boot to Windows but complain a recent software or hardware change has caused windows to not boot properly and select the repair option which would go to the Pre Welcome Splash Screen with a Window stating it was scanning to do a repair, but it would fail.

I removed both of these updates and I haven’t had any issues since on that client’s rig. It made me check my personal rig and I had not put those 2 in.

I just did a WUD check and only one of those updates were showing, I double checked my installed updates and neither are found, so I hid the 1. The other was not found on WUD or my rig.

Reply | Quote

I also wanted to ask

kb3197867- is it safe to install? I guess I’m in Group B (doesn’t like telemetry Patching that Group A has to deal with)

Reply | Quote

Woody,

I’m having the same issue on my windows 8.1 64 bit system that twistedtel has mentioned. I’ve downloaded the security only patch and when trying to install the patch its been stuck on checking for updates on this computer for over 6 hours. I did not disconnect the internet prior to installing the patch. Do you have any suggestions for what I should do?

Thanks,
Jeff

Reply | Quote

Sure. Abort the installation, disconnect from the internet, and try again.

Reply | Quote

If you’re in Group B, yes, kb3197867 is part of the regimen. In the normal course of events you would’ve installed it in November.

http://www.infoworld.com/article/3142903/microsoft-windows/the-time-is-right-to-update-windows-and-office.html

Reply | Quote

That’s my understanding – and why UUP isn’t really a big deal for almost all Win10 customers.

Reply | Quote

Ijust removed all of your subscriptions – you had many!

Reply | Quote

@ abbodi86 & woody ……. The difference in Windows updating between Win XP/7/8.1 n Win 10;…
.
Win XP/7/8.1 = M$-servers scan/check clients’ cptrs n only serve them missing or needed updates as a download file to be installed by the clients’ cptrs, either automatically or manually(ie by clicking certain buttons), as per their WU settings.
……. Hence, prior to July 2015, a running Win 7 SP1 cptr was only served small downloads during every monthly Patch Tuesday, ie less than 50MB , but a clean reinstalled Win 7 SP1 cptr was served a huge download, ie about 1GB or 200 pending security updates, to be installed by the client’s cptr.
.
Win 10 = M$-servers just scan/check clients’ cptrs for their Versions/Editions n serve each Version the same huge cumulative updates as a download file, to be sorted out by the clients’ cptrs as to which ones r needed to be installed automatically.
……. Hence, in Dec 2016, a running Win 10 cptr was served a huge 900+MB(64bit) download file as the cumulative update, and the same clean reinstalled Win 10 cptr was served the same huge download as a cumulative update.
.
.
.
IOW, for Win XP/7/8.1, the Differential Updating happens at M$-servers; while for Win 10, the “Differential Updating” happens at the clients’ cptrs.

By Wiki’s definition, Delta or Differential Updating should be happening at the Software-makers’ servers, n not at the clients’ cptrs. The main purpose of Delta/Differential Updating is to make the regular security update or software upgrade download files smaller.
……. Eg when I did an inplace upgrade from Linux Mint 17.1 to 17.3, only 200MB of updates were downloaded, unpacked/decompressed n installed, compared to the LM 17.3 iso file of 1.5GB. In comparison, an inplace upgrade from Win 10 Version 1511 to 1607 requires a 3GB download file, which is the same size as the Win 10 Version 1607 iso file.
.
arshtechnica and winaero hv stated that Win 10 has no Differential/Delta Updating = huge cumulative update n Version upgrade download files. Whether UUP/Differential Updating will also apply to cumulative updates, time will tell.

Reply | Quote

Hey Woody,

First, thanks for all the work you do to try and help old dummies like me.

I have win7 pro (32bit) and am trying to be in Group B.

Do I install KB3205402, the “rollup” for .NET Framework?

Maybe I have misunderstood you in the past, but I thought you said to NEVER install “quality rollups”?

If I am wrong, please enlighten me!

Thanks!

Reply | Quote

I have win7 pro and am trying to be in Group B.

Do I install KB3205402, the “rollup” for .NET Framework?

Maybe I have misunderstood in the past, but I thought you said to NEVER install “rollups”?

Thanks!

P.S.
Sorry if this I posted this more than once…

Reply | Quote

@100

Thanks for this, and the one below. I have two questions for you, if you don’t mind.

First, you write: “Windows 7 was not so good in the early days. I remember frequent mouse and screen freezes on Windows 7 which may have been due to faulty drivers but this is less important for end users.” Was there a difference, in your experience, between upgrading from Vista or XP vs. a new computer with Win 7 as its first OS installed?

Second, a) do you think Win 10 is getting better or worse and b) would your answer be different for installs over a previous Windows OS vs. a new computer with Win 10 being the first OS installed?

There may have been a third question, but I’ve forgotten it and it’s time for bed. Thanks.

Reply | Quote

UUP is like what updating via Wi-Fi is for iOS.
Updating via iTunes is like installing the full operating system, not only the missing parts.
UUP will be useful only for (phone) upgrades, i.e 1507 to 1511 to 1607.

Reply | Quote

If you’re in Group B, you don’t want anything marked “Rollup” (except the .NET rollups, which are a different kettle of fish). “Rollup” is a catchword for “security and non-security” patches.

Reply | Quote

This month only, the .NET rollup is the same as the .NET security patch. Go figger.

http://www.infoworld.com/article/3153810/microsoft-windows/time-to-update-windows-and-office.html

Reply | Quote

They’re both wrong. Abbodi is right. Win10 only installs the deltas.

Reply | Quote

Excerpts from windowsdotcom; …….
.
“Today, we are ready to roll out to our Windows Insiders an improvement that works across PC, tablet, phone, IoT, and HoloLens. We are announcing the next generation of our delivery technologies incorporated into our latest Insider builds called the Unified Update Platform (UUP).”

Reply | Quote

@Woody:
“Ijust removed all of your subscriptions – you had many!”

I can access ‘manage’ page again. Thank you.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The subscription list reminds me of a thread title.
That narrows a search.
Once on the right thread entering a name, a few words, etc. in the Browser>edit>find & ‘highlight all’ works pretty good. Alternatively the ‘Search Box’ on the Ask
Woody page could help too.

Reply | Quote

I decided to go for Group B. Around 5 p.m. Sunday, I clicked on the Win7 64-bit link and started the Windows Update Standalone Installer. It’s now after 10 a.m. Tuesday and it’s still “searching for updates on this computer,” with the green animated thingy going across the bar. According to my calculations, that’s about 41 hours.
I’ve been just letting it run in the background and continuing working. Is that OK to do?
Last month, I disabled the Windows experience option (I forget what it’s called). And I have it set not to notify me. When I went to the Windows Update program now to see if it has any information it says “Most recent checks for updates: Never.” But it says updates were installed in 9/13/16. But I installed security updates in October, and manually installed MSE updates weekly. (I missed the November updates before you went back to DEFCON 2.)
Do I have to change some setting to get any updates?
Thanks, Morty

Reply | Quote

I just went back in again to check my settings. As per your instructions on Infoworld, I already had it set to “Never check for updates (not recommended).”
Then I checked the box marked “Give me recommended updates the same way I receive important updates.”
But there was no option: “Give me updates for Microsoft products and check for new optional Microsoft software when I update Windows.”
The only other option to check was to “Allow all users to install updates on this computer.” I left that unchecked.
I’m running Windows 7 Enterprise, Version 6.1.7601 Service Pack 1 Build 7601.
Thank you!

Reply | Quote

@Woody:

I’m confused – – – I’ve seen 2 different references. One says “okay” and above it says “NO”.
******************

This is for:

Dec 2016 Security and Quality Rollup for .NET Framework (KB3205404). Listed as Important Update in the Windows Update.
***********************

Please clarify. Thank you.

Reply | Quote

@Woody:

” Is it safe to install the Dec 2016 Security and Quality Rollup for .NET Framework (KB3205404)?”

Also quoted from above:

“Also, will installing KB3205404 still keep me in Group B going forward?”

This is one of the IMPORTANT updates from the Windows Update – – – and I just need clarification as to whether or not it is “safe” to install. In the past the “Security & Quality Rollup for NET” has always been considered to be safe, and installed every month.

Apologies for my confusion, however I just don’t understand.

GROUP B.
Win 7 x64
No other “programs”

Thank you for your help.

Reply | Quote

Yes. This month the net quality and Rollup are the same thing.

Reply | Quote

OK

Reply | Quote

@Mordechai (Morty) Schiller

Poohsticks had a thorough how to posted before, at https://www.askwoody.com/2016/ms-defcon-2-get-patched-and-turn-off-automatic-updates/comment-page-1/#comment-102303

Reply | Quote

Time to move back to MS-DEFCON 2, a new round of unticked Office Updates today.
The current Office updates are superseding many previous updates, so if the previous Office updates were not installed yet, they can wait few more weeks.

Reply | Quote

Install July 2016 rollup update KB3172614 to fix WU scanning permanently

Reply | Quote

UUP will be useful for PC insiders that install preview builds

—

if anybody wany to check how UUP files looks like, check this download link:
https://mega.nz/#F!ptRTgRrD!39YUg_n6IbfhjTtYBzH6WA

they are basically multiple ESD/CAB files, you can use this script pack to convert or gather these files into normal ISO file:
http://www.mirrorcreator.com/files/1KZG5AHJ

Reply | Quote

The “Differential Updating” had been and will still happens at the clients’ machines, that’s the purpose of Windows Update Client

let me simplify how WU works (in all Windows versions):
1- WU sends the proper info for MSFT server
2- WU receives new proper metadata from server
3- WU evaluates these metadata, checks installed updates (if any) and offer the new applicable updates
4- WU downloads small express cab file that holds the update package data manifests
5- WU evaluates the data manifests and finds which parts of the package is applicable, and identify which files are missing based on WinSxS store
6- WU downloads only the missing applicable files in delta generated form using huge patch storage files .psf that contain all the update files deltas
7- WU calls CBS API to perform the installation

Reply | Quote

I had a similar issue with three Windows 10 v1511 boxes and KB3205386. No splash or repair screen, just a “no operating system, trying optical/network” warning. A cold shutdown seemed to fix it. I was assuming hardware problems, but this makes me wonder…

I’m reeealy gonna love this new WinDoze version.

Reply | Quote

Oh boy.

My laptop sustained a fatal blow on Monday. I’m working from my android phone.

Reply | Quote

CAUTION CAUTION CAUTION

Please be sure to check your settings if you change from Windows Update to Microsoft Update (updates for other Microsoft products). When you agree to Microsoft Update there will be a box that gives you a choice between “Recommended Settings” and “keep you current settings” or “Don’t use Recommended settings.”

If you choose “Recommended Settings” or don’t read and just click “OK” it may change your Windows Update to “Automatic Update” as part of the “Recommended Settings.”

Reply | Quote

Thank you, Elly.
But it looks like I missed another train. Will have to wait for the next one to try again to update. And after I just did a full backup, disconnected from the internet and tried again–and it still just kept searching.
With the new DEFCON 2 warning, I’m just going to have to get out my aluminum foil helmet and hope for the best.
Morty

Reply | Quote

@ abbodi86 …….
.
# An inplace upgrade from Win 10 Version 1511 to 1607(32bit) = WU downloads a huge 3GB file.
# A clean install of Win 10 Version 1607(32bit) = downloads a huge 3GB iso file.
……. This means there has been no Differential/Delta updating for Win 10 upgrades or feature updates.
.
# In Dec 2016, an up-to-date n running Win 10 Version 1607(32bit) cptr since 02 Aug 2016, is auto-updated with the Dec 2016 cumulative update = WU downloads a huge 500+MB file.
# Win 10 Version 1607(32bit) is fresh/clean installed on a cptr on Dec 2016 and is auto-updated with the Dec 2016 cumulative update = WU downloads a huge 500+MB file.
……. This means there has been no Differential/Delta updating for Win 10 cumulative updates.
.
Maybe, we hv different interpretation of Differential/Delta updating or UUP.

Reply | Quote

Thank you both for the above advice! This is great help for all of us!!

Reply | Quote

Arghh

Reply | Quote

Woody, this is awful news about your laptop!

Ch100 that is great news to me because I am not succeeding at installing any of the December updates and the Adobe Flash update. See my note under Woody’s announcement regarding the Office updates he made today–no need to occupy space twice.

Reply | Quote

Which part of “WU does not download the whole cumulative update regardless the shown size” is not understandable?
did you try to read any of Windows 10 updates KB articles?

https://support.microsoft.com/en-us/kb/3200970
“If you have installed previous updates, only the new fixes that are contained in this package will be downloaded and installed to your computer. If you are installing a Windows 10 or Windows Server 2016 update package for the first time, the package for the x86 version is 467 MB and the package for the x64 version is 871 MB.”

Reply | Quote

@ abbodi86 ……. Apologies that I could be wrong.

But some Win 10 users hv experienced huge cumulative update downloads in Sep 2016 n onward, …
https://www.tenforums.com/windows-10-news/63552-cumulative-update-kb3189866-windows-10-build-14393-187-a.html

Reply | Quote

@ abbodi86 ……. Any truth(?) to this statement …
“MS seem mighty concerned that buisness users running Windows server update services do not tie up their network bandwidth by installing unneeded updates.To that end PCs on their networks will only download updates they don’t have. What about my internet bandwidth though? The whole cumulative update downloads every month. How big is this going to get ?”
.
…. excerpted from …
http://forum.micromart.co.uk/PrintTopic551153.aspx#

Reply | Quote

As far as i see, most of these issues are related to “Delivery Optimation Service”, not in WU differential algorithm

Yes, i think WSUS admins who want their users to get express downloads like regular WU, are obligated to have each cumulative updates fully downloaded to WSUS server

Reply | Quote

Sorry for late response. Yes, I recently added this functionality to install Office 2016. It sounds like I can just leave this update uninstalled? I am on a volume license if that matters at all.

Reply | Quote

I give up.
This is the third month in a row that I tried to do a Group B update with the Win7 64-bit installer.
This time I left it running for over 30 hours. When I got back to the computer, it was still searching for updates.
So now I have to choose between giving into MS telemetry and moving to Group A or going to the Group W bench and play with pencils.
Sigh….

Reply | Quote

You’re downloading the update from the Catalog and running the MSU file?

Reply | Quote

Did you stop the Windows Update Service before you tried the install? You should do that and retry.

Reply | Quote

Thank you.
I clicked on the link above:
“For those in Group B, the update you want from the Microsoft Catalog is as follows: Win7 64-bit”
and it just kept going for a day and a half.
I’m not sure what you mean by “update from the catalog.” Is that the list of available updates? I never got to a catalog or list.

Reply | Quote

Clicking on that link should’ve downloaded an MSU file. You need to run the file.

Sorry I wasn’t more explicit!

Reply | Quote

I did. And I opted to run the file instead of saving it to my desktop. And it ran for over 30 hours without doing anything. And then I couldn’t even cancel it. I had to go to the taskbar and close the window.
You can’t be more explicit. This is a family website.
Thanks!

Reply | Quote

Thank you!
Two months ago I set Windows Update to “Never.” Is that what you mean?
All the best,
Morty

Reply | Quote

mnffft$#@!

That’s about as explicit as I get.

Try downloading the file, then running it. And before you run it, disconnect the internet.

Any improvement?

Reply | Quote

Thanks again!
I just downloaded the file. Do I have to stop working to run it? Or can it run in the background?

Reply | Quote

I think I just had an aha moment. A senior aha moment.
Maybe I needed to do what you said–to download the file–and then run it “as administrator.”
I’ll try that now and see what happens.
If I don’t get back to you, you’ll know the computer melted.
Thanks again!
Morty

Reply | Quote

No.
Open Control PanelAdministrative ToolsServices
Scroll down and highlight the Windows Update Service
At top left, click on STOP
Now double click on the .msc file you downloaded.
It should go ahead and install

Reply | Quote

@Woody
To do this effectively, you have to stop the WU Service, not just disconnect from the Internet.

Reply | Quote

Run as Admin, and it should run very quickly.

Reply | Quote

I did that. And it’s updating as we speak. I went to my old (should I tell you? — XP machine) to send this while I’m waiting.
Would it be safe to work and let the update run in the background?
Thanks again!
Morty

Reply | Quote

Thank you.
I tried stopping the service, but “stop” was grayed out. So did what Woody said and logged out and then logged in as Administrator. And then…
EUREKA!
It’s running now on the other box.
Thanks again!
Morty

Reply | Quote

Whew!

Reply | Quote

Praise the Lord and thank you and PKCano!
I haven’t had so much fun since I spent hours in the Win 95 Registry cleaning up the debris left by a bad install of McAfee antivirus. I’m too old for this kind of thing!
Now the 64-bit question is, am I OK now, or do I have to go back and get old updates from the last two months that I couldn’t access?
Thanks again and bless you both!
Morty

For the tech-minded, here’s the installer I downloaded:
windows6.1-kb3205394-x64_71d0c657d24bc852f074996c32987fb936c07774.msu

And here’s the the update I got:
Security Update for Windows (KB3205394)
Installation date: ‎Sun ‎1/‎29/‎2017 1:38 PM
Installation status: Successful
Update type: Important
Fix for KB3205394
More information:
http://support.microsoft.com/?kbid=3205394
Help and Support:
http://support.microsoft.com

Reply | Quote

Yep, unfortunately, you have to install the security-only updates for October, November, December and January separately.

Reply | Quote

Just when I thought it was safe!
How do I access the old ones? The msu file only gave me the latest one.
Does the order make a difference?
Thanks again.

Reply | Quote

I don’t think the order makes a difference.

I hope to have a KB article up shortly with the installation sequence. Sorry. I’m overloaded right now, with the conversion to “Phase I” of the Lounge coming up tonight.

In the interim, sit tight. You’ll be OK.

Reply | Quote

Thank you!
With my girth, I usually sit tight.
See you in the lounge. Hope you have wide chairs there.
All the best,
Morty

Reply | Quote

I think there should be a list of specific updates for the reference of those choosing Group B. It is not easy to follow by anyone not using a management tool for this purpose.

Reply | Quote

Use the following links…

October 2016 –

http://www.catalog.update.microsoft.com/Search.aspx?q=october%2B2016%2Bsecurity%20only

November 2016 –

http://www.catalog.update.microsoft.com/Search.aspx?q=november%2B2016%2Bsecurity%20only

December 2016 –

http://www.catalog.update.microsoft.com/Search.aspx?q=december%2B2016%2Bsecurity%20only

January 2017 –

http://www.catalog.update.microsoft.com/Search.aspx?q=january%2B2017%2Bsecurity%20only

Reply | Quote

jmwoods wrote:

Use the following links…

October 2016 –

http://www.catalog.update.microsoft.com/Search.aspx?q=october%2B2016%2Bsecurity%20only

November 2016 –

http://www.catalog.update.microsoft.com/Search.aspx?q=november%2B2016%2Bsecurity%20only

December 2016 –

http://www.catalog.update.microsoft.com/Search.aspx?q=december%2B2016%2Bsecurity%20only

January 2017 –

http://www.catalog.update.microsoft.com/Search.aspx?q=january%2B2017%2Bsecurity%20only

These search links will only work with the English versions of Windows. If you are using another language version (such as Traditional Chinese on mine) these link searches will return nothing.

Hope for the best. Prepare for the worst.

Reply | Quote

Or, use this page to select by month…

https://support.microsoft.com/en-us/help/22801/windows-7-sp1-and-windows-server-2008-r2-sp1-update-history

Reply | Quote

Yes. Excellent. Thank you. (I shoulda remembered that!) Just make sure you get the Security-only patches. Avoid anything called “Rollup” or “Preview.”

Reply | Quote

Thank you!

Reply | Quote

Yes. jmwoods just provided the list. I’ll replicate it when we get the AskWoody Knowledge Base kicked off.

Reply | Quote

Thank you Woody and jmwoods!
This is like having an inside line to Homeland Security.
All the best,
Morty

Reply | Quote

I went through the drill for October. Went in as administrator, downloaded windows 6.1-kb3192391-x64_8acd94d8d268a6507c2852b0d9917f4ae1349b6c.msu, stopped Windows Update in the control panel and ran the installer.
It just kept on “searching this computer….”
I finally gave up.
Microsoft doesn’t like me….
Morty

Reply | Quote

jmwoods wrote:

Use the following links…

October 2016 –

http://www.catalog.update.microsoft.com/Search.aspx?q=october%2B2016%2Bsecurity%20only

November 2016 –

http://www.catalog.update.microsoft.com/Search.aspx?q=november%2B2016%2Bsecurity%20only

December 2016 –

http://www.catalog.update.microsoft.com/Search.aspx?q=december%2B2016%2Bsecurity%20only

January 2017 –

http://www.catalog.update.microsoft.com/Search.aspx?q=january%2B2017%2Bsecurity%20only

one remark:

here – in germany – you won’t hit anything with this search. to use of the update catalog i have to use – i.e. use the proper words for month and security and so on.
maybe it might be easier to maintain a list of KB…. to search to.

Win 10 Pro 1909 x64 (18363.1016)· AMD Ryzen 5 2600X · ASRock X470 Taichi · 64 GB @ 3000 MHz· Desktop
Win 10 Pro 1909 x64 (18363.1016)· Intel i7-8565U · 32 GB @ 1333 MHz ·HP Probook 450 G6
Win 7 Ultimate x64 ESU, Win 8.1 Pro x64, Win 10 Pro 1909 x64, Win 10 Pro 2004 x64, Win 10 Pro 20H2 x64, Win 10 Pro 21H1 x64 20201.1000 (Dev Channel) running on VirtualBox

1 user thanked author for this post.

Morty

Reply | Quote

Find the file number here https://support.microsoft.com/en-us/help/22801/windows-7-sp1-and-windows-server-2008-r2-sp1-update-history

Go to the MS Catalog here http://www.catalog.update.microsoft.com/Home.aspx

Type in just the number (not “KB”) in the search box. BE CAREFUL to get the right bits – 32-bit has no “x86” but 64-bit has x64 – and version.

Reply | Quote

Find the file number here https://support.microsoft.com/en-us/help/22801/windows-7-sp1-and-windows-server-2008-r2-sp1-update-history

Go to the MS Catalog here http://www.catalog.update.microsoft.com/Home.aspx

Type in just the number (not “KB”) in the search box. BE CAREFUL to get the right bits – 32-bit has no “x86” but 64-bit has x64 – and version.
Oh yes – the catalog address works in FireFox as well.

1 user thanked author for this post.

Morty

Reply | Quote

PKCano wrote:

Find the file number here https://support.microsoft.com/en-us/help/22801/windows-7-sp1-and-windows-server-2008-r2-sp1-update-history

Go to the MS Catalog here http://www.catalog.update.microsoft.com/Home.aspx

Type in just the number (not “KB”) in the search box. BE CAREFUL to get the right bits – 32-bit has no “x86” but 64-bit has x64 – and version.
Oh yes – the catalog address works in FireFox as well.

I went through the routine and got this KB number: ​3192391
Then I logged in as Adminitrator and That led me to downloaded this file for Win 7 64 bit:
windows6.1-kb3192391-x64_8acd94d8d268a6507c2852b0d9917f4ae1349b6c (1) Microsoft Update Standalone Package
I went into Windows services and stopped Windows Update and then I disconnected the router and ran the file.
It went for a few hours, until I finally gave up.
Did I do something wrong?
Thanks again, Morty

Reply | Quote

Morty,
That looks like the right file.
Try one more time.
Login as Administrator.
This time set windows Update to “Never check for updates”.
In Services, Stop the Windows Update Service.
Try to install the file again.
Let us know if it works

Reply | Quote

If you continue to have issues, it’s probably prudent to start looking at logs for clues…

Start with the Windows Update log…

1. Click Start, then Run.

2. Cut and paste the following into the Run box…

%windir%\Windowsupdate.log

3. Click OK.

The Windows Update log will open in Notepad.

4. Search for the words FATAL and WARNING (start with FATAL first).

Note: Not all warnings are critical.

5. Post your results.

Thanks again.
I tried going through the routine again before, but it just kept “looking for updates on this computer” or words to that effect.
I tried running %windir%\Windowsupdate.log
But instead of Notepad opening with the log, I got this error message:
C:\Windows\Windowsupdate.log
Application not found

Do I have to run that logged in as Administrator?
Thanks again,
Morty

Reply | Quote

1. Open the C:\Windows folder and search for WindowsUpdate.log

2. If it is there, right click on the file and select “Open with” and select “Choose default program…”

3. Select Notepad, and make sure “Always use the selected program to open this kind of file” is checked.

4. Click OK.

I tried pasting and attaching the update log, but it was too long. So I’m just pasting from the last successful update.
Thanks again,
Morty

Windows Update Client successfully detected 2 updates.
2017-01-26 07:34:09:931 432 b00 Report REPORT EVENT: {BA753383-2D1B-43F4-A9C7-B4A262EDB08A} 2017-01-26 07:34:07:361-0500 1 161 101 {72DB54E5-D6B8-48F8-A6D3-16C39B6E901C} 200 80246001 Microsoft Security Essentials ( Failure Content Download Error: Download failed.
2017-01-26 07:34:11:365 432 b00 Report CWERReporter::HandleEvents – WER report upload completed with status 0x8
2017-01-26 07:34:11:365 432 b00 Report WER Report sent: 7.6.7601.19161 0x80246001(0) 2DB54E5-D6B8-48F8-A6D3-16C39B6E901C Download 200 0 Microsoft Security Essentials ( {7971F918-A847-4430-9279-4A52D1EFE18D} 0
2017-01-26 07:34:34:989 2636 1038 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-26 07:34:34:990 2636 1038 Misc = Process: C:\Program Files (x86)\LogMeIn\x64\LogMeIn.exe
2017-01-26 07:34:34:990 2636 1038 Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-26 07:34:34:989 2636 1038 COMAPI ————-
2017-01-26 07:34:34:990 2636 1038 COMAPI — START — COMAPI: Search [ClientId = LogMeIn]
2017-01-26 07:34:34:990 2636 1038 COMAPI ———
2017-01-26 07:34:35:024 432 b00 Agent *************
2017-01-26 07:34:35:024 2636 1038 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = LogMeIn]
2017-01-26 07:34:35:024 432 b00 Agent ** START ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-26 07:34:35:024 432 b00 Agent *********
2017-01-26 07:34:35:024 432 b00 Agent * Online = No; Ignore download priority = No
2017-01-26 07:34:35:024 432 b00 Agent * Criteria = “IsInstalled = 0 AND IsHidden = 0”
2017-01-26 07:34:35:024 432 b00 Agent * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2017-01-26 07:34:35:024 432 b00 Agent * Search Scope = {Machine}
2017-01-26 07:34:36:782 432 b00 Driver Matched driver to device USB\VID_046D&PID_081A&REV_0010&MI_02
2017-01-26 07:34:36:782 432 b00 Driver Status: 0x180200a, ProblemNumber: 00000000
2017-01-26 07:41:17:054 976 1a08 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-26 07:41:17:054 976 1a08 Misc = Process: c:\Program Files\Microsoft Security Client\MpCmdRun.exe
2017-01-26 07:41:17:054 976 1a08 Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-26 07:41:17:002 976 1a08 COMAPI ————-
2017-01-26 07:41:17:054 976 1a08 COMAPI — START — COMAPI: Search [ClientId = Microsoft Security Essentials (EDB4FA23-53B8-4AFA-8C5D-99752CCA7094)]
2017-01-26 07:41:17:054 976 1a08 COMAPI ———
2017-01-26 07:41:17:103 976 1a08 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = Microsoft Security Essentials (EDB4FA23-53B8-4AFA-8C5D-99752CCA7094)]
2017-01-26 20:03:25:103 432 944 AU AU setting next sqm report timeout to 2017-01-28 01:03:25
2017-01-27 07:30:07:714 6604 13b8 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-27 07:30:07:728 6604 13b8 Misc = Process: C:\Windows\system32\DrvInst.exe
2017-01-27 07:30:07:728 6604 13b8 Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-27 07:30:07:714 6604 13b8 COMAPI ————-
2017-01-27 07:30:07:728 6604 13b8 COMAPI — START — COMAPI: Search [ClientId = ChkWuDrv]
2017-01-27 07:30:07:728 6604 13b8 COMAPI ———
2017-01-27 07:30:08:021 6604 13b8 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = ChkWuDrv]
2017-01-27 07:41:19:387 8152 1ee4 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-27 07:41:19:387 8152 1ee4 Misc = Process: c:\Program Files\Microsoft Security Client\MpCmdRun.exe
2017-01-27 07:41:19:387 8152 1ee4 Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-27 07:41:19:386 8152 1ee4 COMAPI ————-
2017-01-27 07:41:19:387 8152 1ee4 COMAPI — START — COMAPI: Search [ClientId = Microsoft Security Essentials (EDB4FA23-53B8-4AFA-8C5D-99752CCA7094)]
2017-01-27 07:41:19:387 8152 1ee4 COMAPI ———
2017-01-27 07:41:19:390 8152 1ee4 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = Microsoft Security Essentials (EDB4FA23-53B8-4AFA-8C5D-99752CCA7094)]
2017-01-27 11:19:24:303 3936 880 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-27 11:19:24:303 3936 880 Misc = Process: c:\Program Files\Microsoft Security Client\MpCmdRun.exe
2017-01-27 11:19:24:303 3936 880 Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-27 11:19:24:303 3936 880 COMAPI ————-
2017-01-27 11:19:24:303 3936 880 COMAPI — START — COMAPI: Search [ClientId = Microsoft Security Essentials (EDB4FA23-53B8-4AFA-8C5D-99752CCA7094)]
2017-01-27 11:19:24:303 3936 880 COMAPI ———
2017-01-27 11:19:24:318 3936 880 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = Microsoft Security Essentials (EDB4FA23-53B8-4AFA-8C5D-99752CCA7094)]
2017-01-27 14:05:54:996 7504 2314 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-27 14:05:54:996 7504 2314 Misc = Process: C:\Windows\SysWOW64\wusa.exe
2017-01-27 14:05:54:996 7504 2314 Misc = Module: C:\Windows\SysWOW64\wuapi.dll
2017-01-27 14:05:54:995 7504 2314 COMAPI ———– COMAPI: IUpdateServiceManager::AddScanPackageService ———–
2017-01-27 14:05:54:996 7504 2314 COMAPI – ServiceName = Windows Update Standalone Installer
2017-01-27 14:05:54:996 7504 2314 COMAPI – ScanFileLocation = C:\89725c670ad6e510ef21\wsusscan.cab
2017-01-27 14:05:55:268 432 dc8 Misc Validating signature for C:\Windows\SoftwareDistribution\ScanFile\41c02f00-622c-4334-a7f2-b767b6f3c97e\Source.cab with dwProvFlags 0x00000080:
2017-01-27 14:05:55:949 432 dc8 Misc Microsoft signed: Yes
2017-01-27 14:05:56:823 432 dc8 DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2017-01-27 14:05:56:847 7504 2314 COMAPI – Added scan package service, ServiceID = {41C02F00-622C-4334-A7F2-B767B6F3C97E} Third party service
2017-01-27 14:05:56:877 7504 2314 COMAPI ————-
2017-01-27 14:05:56:877 7504 2314 COMAPI — START — COMAPI: Search [ClientId = wusa]
2017-01-27 14:05:56:877 7504 2314 COMAPI ———
2017-01-27 14:05:57:278 7504 2314 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = wusa]
2017-01-27 20:03:25:096 432 944 AU AU setting next sqm report timeout to 2017-01-29 01:03:25
2017-01-28 07:41:16:097 3024 234c Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-28 07:41:16:097 3024 234c Misc = Process: c:\Program Files\Microsoft Security Client\MpCmdRun.exe
2017-01-28 07:41:16:097 3024 234c Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-28 07:41:16:097 3024 234c COMAPI ————-
2017-01-28 07:41:16:097 3024 234c COMAPI — START — COMAPI: Search [ClientId = Microsoft Security Essentials (EDB4FA23-53B8-4AFA-8C5D-99752CCA7094)]
2017-01-28 07:41:16:097 3024 234c COMAPI ———
2017-01-28 07:41:16:097 3024 234c COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = Microsoft Security Essentials (EDB4FA23-53B8-4AFA-8C5D-99752CCA7094)]
2017-01-28 20:03:25:103 432 944 AU AU setting next sqm report timeout to 2017-01-30 01:03:25
2017-01-28 20:49:54:985 432 1cb8 AU Triggering AU detection through DetectNow API
2017-01-28 20:49:55:032 432 1cb8 AU Triggering Online detection (interactive)
2017-01-28 20:49:55:047 432 944 AU #############
2017-01-28 20:49:55:047 432 944 AU ## START ## AU: Search for updates
2017-01-28 20:49:55:047 432 944 AU #########
2017-01-28 20:49:55:079 432 944 AU <<## SUBMITTED ## AU: Search for updates [CallId = {2560B7FD-7C2D-4A0D-B5DA-D9872CF929B1}]
2017-01-28 23:08:28:198 432 944 AU Sending shutdown notification
2017-01-28 23:08:28:198 432 944 AU AU initiates service shutdown
2017-01-28 23:08:28:338 432 944 AU ########### AU: Uninitializing Automatic Updates ###########
2017-01-28 23:08:28:385 432 b00 Agent * WARNING: Failed to filter search results, error = 0x8024000B
2017-01-28 23:08:36:326 432 b00 Agent *********
2017-01-28 23:08:36:326 432 b00 Agent ** END ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-28 23:08:36:326 432 b00 Agent *************
2017-01-28 23:08:38:588 2636 1b8c COMAPI >>– RESUMED — COMAPI: Search [ClientId = LogMeIn]
2017-01-28 23:08:38:619 2636 1b8c COMAPI – Updates found = 0
2017-01-28 23:08:38:619 2636 1b8c COMAPI – WARNING: Exit code = 0x00000000, Result code = 0x8024001E
2017-01-28 23:08:38:619 2636 1b8c COMAPI ———
2017-01-28 23:08:38:619 2636 1b8c COMAPI — END — COMAPI: Search [ClientId = LogMeIn]
2017-01-28 23:08:38:619 2636 1b8c COMAPI ————-
2017-01-28 23:08:38:603 432 944 Agent WARNING: WU client fails to call back to search call {140E7D7C-4B91-4380-8411-D8437393B212} with error 0x800706ba
2017-01-28 23:08:38:634 432 944 Agent WARNING: WU client fails to call back to search call {DAF3D37D-42DC-4532-94EF-B5871D716B7B} with error 0x800706ba
2017-01-28 23:08:38:634 432 944 Agent WARNING: WU client fails to call back to search call {09CE603B-87DB-4276-85E5-8A47F1D39642} with error 0x800706ba
2017-01-28 23:08:38:650 432 944 Agent WARNING: WU client fails to call back to search call {678B79CC-C9A0-4BA5-96FB-18AEF3D869AE} with error 0x800706ba
2017-01-28 23:08:38:650 432 944 Agent WARNING: WU client fails to call back to search call {2EC30223-829C-4501-9259-652F431F1166} with error 0x800706ba
2017-01-28 23:08:38:650 432 944 Agent WARNING: WU client fails to call back to search call {7EF4C422-F2AD-4B05-B4B6-9834A6BF3A88} with error 0x800706ba
2017-01-28 23:08:38:650 432 944 Agent Sending shutdown notification to client
2017-01-28 23:08:38:650 432 944 Agent Sending shutdown notification to client
2017-01-28 23:08:38:650 432 944 Agent Sending shutdown notification to client
2017-01-28 23:08:38:650 2636 216c COMAPI WARNING: Received service shutdown/self-update notification.
2017-01-28 23:08:38:666 432 944 Agent Sending shutdown notification to client
2017-01-28 23:08:38:666 432 944 Agent Sending shutdown notification to client
2017-01-28 23:08:38:666 432 944 Agent Sending shutdown notification to client
2017-01-28 23:08:38:666 432 944 Agent Sending shutdown notification to client
2017-01-28 23:08:38:666 432 944 Agent Sending shutdown notification to client
2017-01-28 23:08:38:666 432 944 Agent Sending shutdown notification to client
2017-01-28 23:08:38:666 432 944 Agent Sending shutdown notification to client
2017-01-28 23:08:38:853 2636 1038 COMAPI WARNING: Operation failed due to earlier error, hr=8024001E
2017-01-28 23:08:38:900 2636 1038 COMAPI FATAL: Unable to complete asynchronous search. (hr=8024001E)
2017-01-28 23:08:41:520 432 944 Service *********
2017-01-28 23:08:41:520 432 944 Service ** END ** Service: Service exit [Exit code = 0x240001]
2017-01-28 23:08:41:520 432 944 Service *************
2017-01-28 23:09:10:521 2636 1038 COMAPI FATAL: Unable to connect to the service (hr=80080005)
2017-01-28 23:09:10:521 2636 1038 COMAPI WARNING: Unable to establish connection to the service. (hr=80080005)
2017-01-28 23:09:10:521 2636 1038 COMAPI ————-
2017-01-28 23:09:10:521 2636 1038 COMAPI — START — COMAPI: Search [ClientId = LogMeIn]
2017-01-28 23:09:10:521 2636 1038 COMAPI ———
2017-01-28 23:09:10:521 2636 1038 COMAPI FATAL: Unable to connect to the service (hr=8007045B)
2017-01-28 23:09:10:521 2636 1038 COMAPI WARNING: Unable to establish connection to the service. (hr=8007045B)
2017-01-28 23:09:10:521 2636 1038 COMAPI – WARNING: Exit code = 0x8007045B
2017-01-28 23:09:10:521 2636 1038 COMAPI ———
2017-01-28 23:09:10:521 2636 1038 COMAPI — END — COMAPI: Search [ClientId = <NULL>]
2017-01-28 23:09:10:521 2636 1038 COMAPI ————-
2017-01-28 23:09:10:521 2636 1038 COMAPI FATAL: Unable to initiate asynchronous search, hr=8007045B
2017-01-28 23:11:14:618 316 568 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-28 23:11:14:618 316 568 Misc = Process: C:\Windows\system32\svchost.exe
2017-01-28 23:11:14:618 316 568 Misc = Module: c:\windows\system32\wuaueng.dll
2017-01-28 23:11:14:618 316 568 Service *************
2017-01-28 23:11:14:618 316 568 Service ** START ** Service: Service startup
2017-01-28 23:11:14:618 316 568 Service *********
2017-01-28 23:11:14:665 316 568 Agent * WU client version 7.6.7601.19161
2017-01-28 23:11:14:665 316 568 Agent * Base directory: C:\Windows\SoftwareDistribution
2017-01-28 23:11:14:665 316 568 Agent * Access type: No proxy
2017-01-28 23:11:14:681 316 568 Agent * Network state: Connected
2017-01-28 23:11:17:551 316 630 Report CWERReporter::Init succeeded
2017-01-28 23:11:17:551 316 630 Agent *********** Agent: Initializing Windows Update Agent ***********
2017-01-28 23:11:17:551 316 630 Agent * Prerequisite roots succeeded.
2017-01-28 23:11:17:551 316 630 Agent *********** Agent: Initializing global settings cache ***********
2017-01-28 23:11:17:551 316 630 Agent * WSUS server: <NULL>
2017-01-28 23:11:17:551 316 630 Agent * WSUS status server: <NULL>
2017-01-28 23:11:17:551 316 630 Agent * Target group: (Unassigned Computers)
2017-01-28 23:11:17:551 316 630 Agent * Windows Update access disabled: No
2017-01-28 23:11:17:551 316 630 Agent * Found 1 persisted download calls to restore
2017-01-28 23:11:17:551 316 630 Agent WARNING: WU client failed to initialize a download call from persisted data with potential error 0x80248002
2017-01-28 23:11:17:551 316 630 DnldMgr Download manager restoring 0 downloads
2017-01-28 23:11:17:551 316 630 Agent * Failed to load persisted download calls, error = 0x80248002
2017-01-28 23:11:18:238 316 568 Report *********** Report: Initializing static reporting data ***********
2017-01-28 23:11:18:238 316 568 Report * OS Version = 6.1.7601.1.0.65792
2017-01-28 23:11:18:238 316 568 Report * OS Product Type = 0x00000004
2017-01-28 23:11:18:253 316 568 Report * Computer Brand = Hewlett-Packard
2017-01-28 23:11:18:253 316 568 Report * Computer Model = HP xw4400 Workstation
2017-01-28 23:11:18:269 316 568 Report * Bios Revision = 786D7 v02.03
2017-01-28 23:11:18:269 316 568 Report * Bios Name = Default System BIOS
2017-01-28 23:11:18:269 316 568 Report * Bios Release Date = 2006-04-04T00:00:00
2017-01-28 23:11:18:269 316 568 Report * Locale ID = 1033
2017-01-28 23:11:19:252 2316 b0c Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-28 23:11:19:252 2316 b0c Misc = Process: C:\Program Files (x86)\LogMeIn\x64\LogMeIn.exe
2017-01-28 23:11:19:252 2316 b0c Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-28 23:11:19:252 2316 b0c COMAPI ————-
2017-01-28 23:11:19:252 2316 b0c COMAPI — START — COMAPI: Search [ClientId = LogMeIn]
2017-01-28 23:11:19:252 2316 b0c COMAPI ———
2017-01-28 23:11:19:252 2316 b0c COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = LogMeIn]
2017-01-28 23:11:23:230 316 c4c Agent *************
2017-01-28 23:11:23:230 316 c4c Agent ** START ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-28 23:11:23:230 316 c4c Agent *********
2017-01-28 23:11:23:230 316 c4c Agent * Online = No; Ignore download priority = No
2017-01-28 23:11:23:230 316 c4c Agent * Criteria = “IsInstalled = 0 AND IsHidden = 0”
2017-01-28 23:11:23:230 316 c4c Agent * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2017-01-28 23:11:23:230 316 c4c Agent * Search Scope = {Machine}
2017-01-28 23:11:24:556 316 c4c Driver Matched driver to device USB\VID_046D&PID_081A&REV_0010&MI_02
2017-01-28 23:11:24:556 316 c4c Driver Status: 0x180200a, ProblemNumber: 00000000
2017-01-28 23:12:02:448 316 568 AU ########### AU: Initializing Automatic Updates ###########
2017-01-28 23:12:02:464 316 568 AU # AU disabled through User preference
2017-01-28 23:12:02:495 316 568 AU Initializing featured updates
2017-01-28 23:12:02:495 316 568 AU Found 0 cached featured updates
2017-01-28 23:12:02:526 316 568 AU Successfully wrote event for AU health state:0
2017-01-28 23:12:02:526 316 568 AU Successfully wrote event for AU health state:0
2017-01-28 23:12:02:526 316 568 AU AU finished delayed initialization
2017-01-28 23:20:22:257 3976 e54 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-28 23:20:22:257 3976 e54 Misc = Process: c:\Program Files\Microsoft Security Client\MpCmdRun.exe
2017-01-28 23:20:22:257 3976 e54 Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-28 23:20:22:257 3976 e54 COMAPI ————-
2017-01-28 23:20:22:257 3976 e54 COMAPI — START — COMAPI: Search [ClientId = Microsoft Security Essentials (EDB4FA23-53B8-4AFA-8C5D-99752CCA7094)]
2017-01-28 23:20:22:257 3976 e54 COMAPI ———
2017-01-28 23:20:22:257 3976 e54 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = Microsoft Security Essentials (EDB4FA23-53B8-4AFA-8C5D-99752CCA7094)]
2017-01-29 12:57:16:313 6024 10c8 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-29 12:57:16:329 6024 10c8 Misc = Process: C:\Windows\system32\wusa.exe
2017-01-29 12:57:16:329 6024 10c8 Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-29 12:57:16:313 6024 10c8 COMAPI ———– COMAPI: IUpdateServiceManager::AddScanPackageService ———–
2017-01-29 12:57:16:329 6024 10c8 COMAPI – ServiceName = Windows Update Standalone Installer
2017-01-29 12:57:16:329 6024 10c8 COMAPI – ScanFileLocation = C:\5e137cfd182a4ce1269c606f1c181a\wsusscan.cab
2017-01-29 12:57:16:376 316 14d4 Misc Validating signature for C:\Windows\SoftwareDistribution\ScanFile\02ae5ecc-230b-4d58-8524-e8f3f9e4414e\Source.cab with dwProvFlags 0x00000080:
2017-01-29 12:57:16:578 316 14d4 Misc Microsoft signed: Yes
2017-01-29 12:57:16:672 316 14d4 DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2017-01-29 12:57:16:688 6024 10c8 COMAPI – Added scan package service, ServiceID = {02AE5ECC-230B-4D58-8524-E8F3F9E4414E} Third party service
2017-01-29 12:57:16:688 6024 10c8 COMAPI ————-
2017-01-29 12:57:16:688 6024 10c8 COMAPI — START — COMAPI: Search [ClientId = wusa]
2017-01-29 12:57:16:688 6024 10c8 COMAPI ———
2017-01-29 12:57:16:703 6024 10c8 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = wusa]
2017-01-29 13:15:59:695 316 568 AU Sending shutdown notification
2017-01-29 13:15:59:695 316 568 AU AU initiates service shutdown
2017-01-29 13:15:59:711 316 568 AU ########### AU: Uninitializing Automatic Updates ###########
2017-01-29 13:15:59:711 316 c4c Agent * WARNING: Failed to filter search results, error = 0x8024000B
2017-01-29 13:16:00:459 316 c4c Agent *********
2017-01-29 13:16:00:459 316 c4c Agent ** END ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-29 13:16:00:459 316 c4c Agent *************
2017-01-29 13:16:00:459 2316 14e0 COMAPI >>– RESUMED — COMAPI: Search [ClientId = LogMeIn]
2017-01-29 13:16:00:459 2316 14e0 COMAPI – Updates found = 0
2017-01-29 13:16:00:459 2316 14e0 COMAPI – WARNING: Exit code = 0x00000000, Result code = 0x8024001E
2017-01-29 13:16:00:459 2316 14e0 COMAPI ———
2017-01-29 13:16:00:459 2316 14e0 COMAPI — END — COMAPI: Search [ClientId = LogMeIn]
2017-01-29 13:16:00:459 2316 14e0 COMAPI ————-
2017-01-29 13:16:00:459 316 568 Agent WARNING: WU client fails to call back to search call {64B13757-028D-4C90-955D-96CBBCEDB574} with error 0x800706ba
2017-01-29 13:16:00:491 316 568 Agent WARNING: WU client fails to call back to search call {19A6C1FA-C530-4957-9E80-D65674C8373E} with error 0x800706ba
2017-01-29 13:16:00:491 316 568 Agent Sending shutdown notification to client
2017-01-29 13:16:00:491 2316 161c COMAPI WARNING: Received service shutdown/self-update notification.
2017-01-29 13:16:00:491 316 568 Agent Sending shutdown notification to client
2017-01-29 13:16:00:491 316 568 Agent Sending shutdown notification to client
2017-01-29 13:16:00:491 316 568 Agent Sending shutdown notification to client
2017-01-29 13:16:00:459 2316 b0c COMAPI WARNING: Operation failed due to earlier error, hr=8024001E
2017-01-29 13:16:00:491 2316 b0c COMAPI FATAL: Unable to complete asynchronous search. (hr=8024001E)
2017-01-29 13:16:01:037 316 568 Service *********
2017-01-29 13:16:01:037 316 568 Service ** END ** Service: Service exit [Exit code = 0x240001]
2017-01-29 13:16:01:037 316 568 Service *************
2017-01-29 13:16:32:455 2316 b0c COMAPI FATAL: Unable to connect to the service (hr=80080005)
2017-01-29 13:16:32:455 2316 b0c COMAPI WARNING: Unable to establish connection to the service. (hr=80080005)
2017-01-29 13:16:32:455 2316 b0c COMAPI ————-
2017-01-29 13:16:32:455 2316 b0c COMAPI — START — COMAPI: Search [ClientId = LogMeIn]
2017-01-29 13:16:32:455 2316 b0c COMAPI ———
2017-01-29 13:16:32:455 2316 b0c COMAPI FATAL: Unable to connect to the service (hr=8007045B)
2017-01-29 13:16:32:455 2316 b0c COMAPI WARNING: Unable to establish connection to the service. (hr=8007045B)
2017-01-29 13:16:32:455 2316 b0c COMAPI – WARNING: Exit code = 0x8007045B
2017-01-29 13:16:32:455 2316 b0c COMAPI ———
2017-01-29 13:16:32:455 2316 b0c COMAPI — END — COMAPI: Search [ClientId = <NULL>]
2017-01-29 13:16:32:455 2316 b0c COMAPI ————-
2017-01-29 13:16:32:455 2316 b0c COMAPI FATAL: Unable to initiate asynchronous search, hr=8007045B
2017-01-29 13:20:41:627 396 168c Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-29 13:20:41:627 396 168c Misc = Process: C:\Windows\system32\svchost.exe
2017-01-29 13:20:41:627 396 168c Misc = Module: c:\windows\system32\wuaueng.dll
2017-01-29 13:20:41:627 396 168c Service *************
2017-01-29 13:20:41:627 396 168c Service ** START ** Service: Service startup
2017-01-29 13:20:41:627 396 168c Service *********
2017-01-29 13:20:41:955 396 168c Agent * WU client version 7.6.7601.19161
2017-01-29 13:20:41:971 396 168c Agent * Base directory: C:\Windows\SoftwareDistribution
2017-01-29 13:20:41:971 396 168c Agent * Access type: No proxy
2017-01-29 13:20:42:033 396 168c Agent * Network state: Connected
2017-01-29 13:20:45:095 396 5fc Report CWERReporter::Init succeeded
2017-01-29 13:20:45:095 396 5fc Agent *********** Agent: Initializing Windows Update Agent ***********
2017-01-29 13:20:45:110 396 5fc Agent * Prerequisite roots succeeded.
2017-01-29 13:20:45:110 396 5fc Agent *********** Agent: Initializing global settings cache ***********
2017-01-29 13:20:45:110 396 5fc Agent * WSUS server: <NULL>
2017-01-29 13:20:45:110 396 5fc Agent * WSUS status server: <NULL>
2017-01-29 13:20:45:110 396 5fc Agent * Target group: (Unassigned Computers)
2017-01-29 13:20:45:110 396 5fc Agent * Windows Update access disabled: No
2017-01-29 13:20:45:188 396 5fc Agent * Found 1 persisted download calls to restore
2017-01-29 13:20:45:204 396 5fc Agent WARNING: WU client failed to initialize a download call from persisted data with potential error 0x80248002
2017-01-29 13:20:45:204 396 5fc DnldMgr Download manager restoring 0 downloads
2017-01-29 13:20:45:219 396 5fc Agent * Failed to load persisted download calls, error = 0x80248002
2017-01-29 13:20:46:999 396 168c Report *********** Report: Initializing static reporting data ***********
2017-01-29 13:20:46:999 396 168c Report * OS Version = 6.1.7601.1.0.65792
2017-01-29 13:20:46:999 396 168c Report * OS Product Type = 0x00000004
2017-01-29 13:20:47:202 396 168c Report * Computer Brand = Hewlett-Packard
2017-01-29 13:20:47:202 396 168c Report * Computer Model = HP xw4400 Workstation
2017-01-29 13:20:47:202 396 168c Report * Bios Revision = 786D7 v02.03
2017-01-29 13:20:47:202 396 168c Report * Bios Name = Default System BIOS
2017-01-29 13:20:47:202 396 168c Report * Bios Release Date = 2006-04-04T00:00:00
2017-01-29 13:20:47:202 396 168c Report * Locale ID = 1033
2017-01-29 13:21:08:331 4580 12f0 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-29 13:21:08:331 4580 12f0 Misc = Process: C:\Program Files (x86)\LogMeIn\x64\LogMeIn.exe
2017-01-29 13:21:08:331 4580 12f0 Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-29 13:21:08:331 4580 12f0 COMAPI ————-
2017-01-29 13:21:08:331 4580 12f0 COMAPI — START — COMAPI: Search [ClientId = LogMeIn]
2017-01-29 13:21:08:331 4580 12f0 COMAPI ———
2017-01-29 13:21:09:533 4580 12f0 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = LogMeIn]
2017-01-29 13:21:12:615 396 b4c Agent *************
2017-01-29 13:21:12:615 396 b4c Agent ** START ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-29 13:21:12:615 396 b4c Agent *********
2017-01-29 13:21:12:615 396 b4c Agent * Online = No; Ignore download priority = No
2017-01-29 13:21:12:615 396 b4c Agent * Criteria = “IsInstalled = 0 AND IsHidden = 0”
2017-01-29 13:21:12:615 396 b4c Agent * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2017-01-29 13:21:12:615 396 b4c Agent * Search Scope = {Machine}
2017-01-29 13:21:15:563 396 b4c Driver Matched driver to device USB\VID_046D&PID_081A&REV_0010&MI_02
2017-01-29 13:21:15:563 396 b4c Driver Status: 0x180200a, ProblemNumber: 00000000
2017-01-29 13:21:29:965 396 168c AU ########### AU: Initializing Automatic Updates ###########
2017-01-29 13:21:29:996 396 168c AU # AU disabled through User preference
2017-01-29 13:21:30:027 396 168c AU Initializing featured updates
2017-01-29 13:21:30:027 396 168c AU Found 0 cached featured updates
2017-01-29 13:21:30:058 396 168c AU Successfully wrote event for AU health state:0
2017-01-29 13:21:30:058 396 168c AU Successfully wrote event for AU health state:0
2017-01-29 13:21:30:058 396 168c AU AU finished delayed initialization
2017-01-29 13:27:52:712 396 168c AU ########### AU: Uninitializing Automatic Updates ###########
2017-01-29 13:27:52:712 396 b4c Agent * WARNING: Failed to filter search results, error = 0x8024000B
2017-01-29 13:27:52:728 396 b4c Agent *********
2017-01-29 13:27:52:728 396 b4c Agent ** END ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-29 13:27:52:728 396 b4c Agent *************
2017-01-29 13:27:52:744 4580 154c COMAPI >>– RESUMED — COMAPI: Search [ClientId = LogMeIn]
2017-01-29 13:27:52:744 4580 154c COMAPI – Updates found = 0
2017-01-29 13:27:52:744 4580 154c COMAPI – WARNING: Exit code = 0x00000000, Result code = 0x8024001E
2017-01-29 13:27:52:744 4580 154c COMAPI ———
2017-01-29 13:27:52:744 4580 154c COMAPI — END — COMAPI: Search [ClientId = LogMeIn]
2017-01-29 13:27:52:744 4580 154c COMAPI ————-
2017-01-29 13:27:52:744 396 168c Agent Sending shutdown notification to client
2017-01-29 13:27:52:744 4580 12f0 COMAPI WARNING: Operation failed due to earlier error, hr=8024001E
2017-01-29 13:27:52:744 4580 13b8 COMAPI WARNING: Received service shutdown/self-update notification.
2017-01-29 13:27:52:744 4580 12f0 COMAPI FATAL: Unable to complete asynchronous search. (hr=8024001E)
2017-01-29 13:27:53:508 396 168c Service *********
2017-01-29 13:27:53:508 396 168c Service ** END ** Service: Service exit [Exit code = 0x240001]
2017-01-29 13:27:53:508 396 168c Service *************
2017-01-29 13:29:07:151 1824 1440 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-29 13:29:07:151 1824 1440 Misc = Process: C:\Windows\system32\wusa.exe
2017-01-29 13:29:07:151 1824 1440 Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-29 13:29:07:151 1824 1440 COMAPI ———– COMAPI: IUpdateServiceManager::AddScanPackageService ———–
2017-01-29 13:29:07:151 1824 1440 COMAPI – ServiceName = Windows Update Standalone Installer
2017-01-29 13:29:07:151 1824 1440 COMAPI – ScanFileLocation = C:\d90c860df4626471b24f\wsusscan.cab
2017-01-29 13:29:07:166 396 e2c Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-29 13:29:07:166 396 e2c Misc = Process: C:\Windows\system32\svchost.exe
2017-01-29 13:29:07:166 396 e2c Misc = Module: c:\windows\system32\wuaueng.dll
2017-01-29 13:29:07:166 396 e2c Service *************
2017-01-29 13:29:07:166 396 e2c Service ** START ** Service: Service startup
2017-01-29 13:29:07:166 396 e2c Service *********
2017-01-29 13:29:07:166 396 e2c Agent * WU client version 7.6.7601.19161
2017-01-29 13:29:07:166 396 e2c Agent * Base directory: C:\Windows\SoftwareDistribution
2017-01-29 13:29:07:166 396 e2c Agent * Access type: No proxy
2017-01-29 13:29:07:166 396 e2c Agent * Network state: Connected
2017-01-29 13:29:07:229 396 1f8 Report CWERReporter::Init succeeded
2017-01-29 13:29:07:229 396 1f8 Agent *********** Agent: Initializing Windows Update Agent ***********
2017-01-29 13:29:07:229 396 1f8 Agent * Prerequisite roots succeeded.
2017-01-29 13:29:07:229 396 1f8 Agent *********** Agent: Initializing global settings cache ***********
2017-01-29 13:29:07:229 396 1f8 Agent * WSUS server: <NULL>
2017-01-29 13:29:07:229 396 1f8 Agent * WSUS status server: <NULL>
2017-01-29 13:29:07:229 396 1f8 Agent * Target group: (Unassigned Computers)
2017-01-29 13:29:07:229 396 1f8 Agent * Windows Update access disabled: No
2017-01-29 13:29:07:229 396 1f8 Agent * Found 1 persisted download calls to restore
2017-01-29 13:29:07:229 396 1f8 Agent WARNING: WU client failed to initialize a download call from persisted data with potential error 0x80248002
2017-01-29 13:29:07:229 396 1f8 DnldMgr Download manager restoring 0 downloads
2017-01-29 13:29:07:229 396 1f8 Agent * Failed to load persisted download calls, error = 0x80248002
2017-01-29 13:29:07:276 396 1018 Misc Validating signature for C:\Windows\SoftwareDistribution\ScanFile\eeb6cf27-9aa0-4004-a0c3-9ccfd5a16db5\Source.cab with dwProvFlags 0x00000080:
2017-01-29 13:29:07:666 396 e2c Report *********** Report: Initializing static reporting data ***********
2017-01-29 13:29:07:666 396 e2c Report * OS Version = 6.1.7601.1.0.65792
2017-01-29 13:29:07:666 396 e2c Report * OS Product Type = 0x00000004
2017-01-29 13:29:07:681 396 1018 Misc Microsoft signed: Yes
2017-01-29 13:29:07:681 396 e2c Report * Computer Brand = Hewlett-Packard
2017-01-29 13:29:07:681 396 e2c Report * Computer Model = HP xw4400 Workstation
2017-01-29 13:29:07:681 396 e2c Report * Bios Revision = 786D7 v02.03
2017-01-29 13:29:07:681 396 e2c Report * Bios Name = Default System BIOS
2017-01-29 13:29:07:681 396 e2c Report * Bios Release Date = 2006-04-04T00:00:00
2017-01-29 13:29:07:681 396 e2c Report * Locale ID = 1033
2017-01-29 13:29:07:712 396 1018 DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2017-01-29 13:29:07:712 1824 1440 COMAPI – Added scan package service, ServiceID = {EEB6CF27-9AA0-4004-A0C3-9CCFD5A16DB5} Third party service
2017-01-29 13:29:07:712 1824 1440 COMAPI ————-
2017-01-29 13:29:07:712 1824 1440 COMAPI — START — COMAPI: Search [ClientId = wusa]
2017-01-29 13:29:07:712 1824 1440 COMAPI ———
2017-01-29 13:29:07:712 1824 1440 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = wusa]
2017-01-29 13:29:07:822 396 12a0 Agent *************
2017-01-29 13:29:07:822 396 12a0 Agent ** START ** Agent: Finding updates [CallerId = wusa]
2017-01-29 13:29:07:822 396 12a0 Agent *********
2017-01-29 13:29:07:822 396 12a0 Agent * Online = Yes; Ignore download priority = No
2017-01-29 13:29:07:822 396 12a0 Agent * Criteria = “DeploymentAction=’Installation'”
2017-01-29 13:29:07:822 396 12a0 Agent * ServiceID = {EEB6CF27-9AA0-4004-A0C3-9CCFD5A16DB5} Third party service
2017-01-29 13:29:07:822 396 12a0 Agent * Search Scope = {Machine}
2017-01-29 13:29:08:102 396 12a0 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2017-01-29 13:29:08:102 396 12a0 PT + Offline serviceId = {EEB6CF27-9AA0-4004-A0C3-9CCFD5A16DB5}
2017-01-29 13:29:08:134 396 12a0 PT WARNING: Cached cookie has expired or new PID is available
2017-01-29 13:29:16:812 396 12a0 PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2017-01-29 13:29:16:812 396 12a0 PT + Offline serviceId = {EEB6CF27-9AA0-4004-A0C3-9CCFD5A16DB5}
2017-01-29 13:29:17:109 396 12a0 Agent * Added update {15A18FD4-240A-49EA-B9A9-936139646AC8}.501 to search result
2017-01-29 13:29:17:109 396 12a0 Agent * Found 1 updates and 59 categories in search; evaluated appl. rules of 126 out of 371 deployed entities
2017-01-29 13:29:17:171 396 12a0 Agent *********
2017-01-29 13:29:17:171 396 12a0 Agent ** END ** Agent: Finding updates [CallerId = wusa]
2017-01-29 13:29:17:171 396 12a0 Agent *************
2017-01-29 13:29:17:171 1824 1720 COMAPI >>– RESUMED — COMAPI: Search [ClientId = wusa]
2017-01-29 13:29:17:233 1824 1720 COMAPI – Updates found = 1
2017-01-29 13:29:17:233 1824 1720 COMAPI ———
2017-01-29 13:29:17:233 1824 1720 COMAPI — END — COMAPI: Search [ClientId = wusa]
2017-01-29 13:29:17:233 1824 1720 COMAPI ————-
2017-01-29 13:29:21:196 396 15dc DnldMgr *********** DnldMgr: Copy update to cache [UpdateId = {24431A5C-250C-467F-B942-264AC423CF92}.501] ***********
2017-01-29 13:29:21:243 396 15dc DnldMgr Asking handler to generate non-range requests.
2017-01-29 13:29:21:243 396 15dc Handler Generating request for CBS update 24431A5C-250C-467F-B942-264AC423CF92 in sandbox C:\Windows\SoftwareDistribution\Download\cb3c1b8236a14753b9612c2cd8a11a9c_ctc
2017-01-29 13:29:21:243 396 15dc Handler Selecting self-contained because update does not have express payload.
2017-01-29 13:29:21:243 396 15dc Handler Selected payload type is ptSelfContained
2017-01-29 13:29:21:258 396 15dc Handler Detected download state is dsStart
2017-01-29 13:29:21:258 396 15dc Handler Adding Windows6.1-KB3205394-x64.cab (entire file) to request list.
2017-01-29 13:29:21:274 396 15dc Handler Request generation for CBS update complete with hr=0x0 and pfResetSandbox=0
2017-01-29 13:29:21:804 396 15dc Misc Validating signature for C:\Windows\SoftwareDistribution\Download\cb3c1b8236a14753b9612c2cd8a11a9c_ctc\Windows6.1-KB3205394-x64.cab with dwProvFlags 0x00000080:
2017-01-29 13:29:23:052 396 15dc Misc Microsoft signed: Yes
2017-01-29 13:29:23:052 396 15dc DnldMgr Asking handler to generate non-range requests.
2017-01-29 13:29:23:052 396 15dc Handler Generating request for CBS update 24431A5C-250C-467F-B942-264AC423CF92 in sandbox C:\Windows\SoftwareDistribution\Download\cb3c1b8236a14753b9612c2cd8a11a9c_ctc
2017-01-29 13:29:23:052 396 15dc Handler Selecting self-contained because update does not have express payload.
2017-01-29 13:29:23:052 396 15dc Handler Selected payload type is ptSelfContained
2017-01-29 13:29:23:052 396 15dc Handler Detected download state is dsHavePackage
2017-01-29 13:29:23:052 396 15dc Handler Request generation for CBS update complete with hr=0x0 and pfResetSandbox=0
2017-01-29 13:29:23:115 1824 1440 COMAPI ————-
2017-01-29 13:29:23:115 1824 1440 COMAPI — START — COMAPI: Install [ClientId = wusa]
2017-01-29 13:29:23:115 1824 1440 COMAPI ———
2017-01-29 13:29:23:115 1824 1440 COMAPI – Allow source prompts: Yes; Forced: No; Force quiet: No
2017-01-29 13:29:23:115 1824 1440 COMAPI – Updates in request: 1
2017-01-29 13:29:23:115 1824 1440 COMAPI – ServiceID = {EEB6CF27-9AA0-4004-A0C3-9CCFD5A16DB5} Third party service
2017-01-29 13:29:23:130 1824 1440 COMAPI – Updates to install = 1
2017-01-29 13:29:23:130 1824 1440 COMAPI <<– SUBMITTED — COMAPI: Install [ClientId = wusa]
2017-01-29 13:29:23:130 396 cfc Agent *************
2017-01-29 13:29:23:130 396 cfc Agent ** START ** Agent: Installing updates [CallerId = wusa]
2017-01-29 13:29:23:130 396 cfc Agent *********
2017-01-29 13:29:23:130 396 cfc Agent * Updates to install = 1
2017-01-29 13:29:23:130 396 cfc Agent * Title = Security Update for Windows (KB3205394)
2017-01-29 13:29:23:130 396 cfc Agent * UpdateId = {15A18FD4-240A-49EA-B9A9-936139646AC8}.501
2017-01-29 13:29:23:130 396 cfc Agent * Bundles 1 updates:
2017-01-29 13:29:23:130 396 cfc Agent * {24431A5C-250C-467F-B942-264AC423CF92}.501
2017-01-29 13:29:52:214 396 e2c AU ########### AU: Initializing Automatic Updates ###########
2017-01-29 13:29:52:214 396 e2c AU # AU disabled through User preference
2017-01-29 13:29:55:599 396 e2c AU Initializing featured updates
2017-01-29 13:29:55:599 396 e2c AU Found 0 cached featured updates
2017-01-29 13:29:55:599 396 e2c AU Successfully wrote event for AU health state:0
2017-01-29 13:29:55:599 396 e2c AU Successfully wrote event for AU health state:0
2017-01-29 13:29:55:599 396 e2c AU AU finished delayed initialization
2017-01-29 13:30:00:591 396 cfc Handler Attempting to create remote handler process as Admin-PC\Admin in session 1
2017-01-29 13:30:01:012 396 cfc DnldMgr Preparing update for install, updateId = {24431A5C-250C-467F-B942-264AC423CF92}.501.
2017-01-29 13:30:01:028 3040 17fc Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-29 13:30:01:028 3040 17fc Misc = Process: C:\Windows\system32\wuauclt.exe
2017-01-29 13:30:01:028 3040 17fc Misc = Module: C:\Windows\system32\wuaueng.dll
2017-01-29 13:30:01:028 3040 17fc Handler :::::::::::::
2017-01-29 13:30:01:028 3040 17fc Handler :: START :: Handler: CBS Install
2017-01-29 13:30:01:028 3040 17fc Handler :::::::::
2017-01-29 13:30:01:028 3040 17fc Handler Starting install of CBS update 24431A5C-250C-467F-B942-264AC423CF92
2017-01-29 13:30:01:168 3040 17fc Handler CBS package identity: Package_for_KB3205394~31bf3856ad364e35~amd64~~6.1.1.3
2017-01-29 13:30:01:278 3040 17fc Handler Installing self-contained with source=C:\Windows\SoftwareDistribution\Download\cb3c1b8236a14753b9612c2cd8a11a9c\Windows6.1-KB3205394-x64.cab, workingdir=C:\Windows\SoftwareDistribution\Download\cb3c1b8236a14753b9612c2cd8a11a9c\inst
2017-01-29 13:30:05:772 396 12a0 Report REPORT EVENT: {97C4C411-6AFE-4379-BC74-2345E66EF04C} 2017-01-29 13:30:00:591-0500 1 181 101 {15A18FD4-240A-49EA-B9A9-936139646AC8} 501 0 wusa Success Content Install Installation Started: Windows successfully started the following update: Security Update for Windows (KB3205394)
2017-01-29 13:38:07:029 3040 17fc Handler Requesting post-reboot reporting for package Package_for_KB3205394~31bf3856ad364e35~amd64~~6.1.1.3.
2017-01-29 13:38:07:029 3040 17fc Handler Completed install of CBS update with type=3, requiresReboot=1, installerError=0, hr=0x0
2017-01-29 13:38:07:029 3040 17fc Handler :::::::::
2017-01-29 13:38:07:029 3040 17fc Handler :: END :: Handler: CBS Install
2017-01-29 13:38:07:029 3040 17fc Handler :::::::::::::
2017-01-29 13:38:07:466 396 cfc Agent LogHistory called. idUpdate={15A18FD4-240A-49EA-B9A9-936139646AC8}.501, resultMapped=80242014, resultUnMapped=0
2017-01-29 13:38:14:174 396 cfc Agent *********
2017-01-29 13:38:14:174 396 cfc Agent ** END ** Agent: Installing updates [CallerId = wusa]
2017-01-29 13:38:14:174 396 cfc Agent *************
2017-01-29 13:38:14:174 396 e2c AU Can not perform non-interactive scan if AU is interactive-only
2017-01-29 13:38:14:174 1824 c7c COMAPI >>– RESUMED — COMAPI: Install [ClientId = wusa]
2017-01-29 13:38:14:174 1824 c7c COMAPI – Install call complete (succeeded = 1, succeeded with errors = 0, failed = 0, unaccounted = 0)
2017-01-29 13:38:14:174 1824 c7c COMAPI – Reboot required = Yes
2017-01-29 13:38:14:174 1824 c7c COMAPI ———
2017-01-29 13:38:14:174 1824 c7c COMAPI — END — COMAPI: Install [ClientId = wusa]
2017-01-29 13:38:14:174 1824 c7c COMAPI ————-
2017-01-29 13:46:16:144 1824 1440 COMAPI Installation wizard (API) invoking RebootSystem
2017-01-29 13:46:16:331 1824 1440 Misc WARNING: SUS Client is rebooting system.
2017-01-29 13:46:16:331 1824 1440 COMAPI ———– COMAPI: IUpdateServiceManager::RemoveService ———–
2017-01-29 13:46:16:331 1824 1440 COMAPI – ServiceId = {eeb6cf27-9aa0-4004-a0c3-9ccfd5a16db5}
2017-01-29 13:46:19:202 1824 1440 COMAPI IUpdateService removing volatile scan package service, serviceID = {EEB6CF27-9AA0-4004-A0C3-9CCFD5A16DB5}
2017-01-29 13:46:19:202 396 11cc Agent WARNING: WU client fails CClientCallRecorder::RemoveService with error 0x80248014
2017-01-29 13:46:19:202 1824 1440 COMAPI WARNING: ISusInternal::RemoveService failed, hr=80248014
2017-01-29 13:46:28:430 396 e2c AU Sending shutdown notification
2017-01-29 13:46:28:430 396 e2c AU AU initiates service shutdown
2017-01-29 13:46:28:446 396 e2c AU ########### AU: Uninitializing Automatic Updates ###########
2017-01-29 13:46:29:678 396 e2c Service *********
2017-01-29 13:46:29:694 396 e2c Service ** END ** Service: Service exit [Exit code = 0x240001]
2017-01-29 13:46:29:694 396 e2c Service *************
2017-01-29 13:52:05:459 420 bf8 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-29 13:52:05:459 420 bf8 Misc = Process: C:\Windows\system32\svchost.exe
2017-01-29 13:52:05:459 420 bf8 Misc = Module: c:\windows\system32\wuaueng.dll
2017-01-29 13:52:05:459 420 bf8 Service *************
2017-01-29 13:52:05:459 420 bf8 Service ** START ** Service: Service startup
2017-01-29 13:52:05:459 420 bf8 Service *********
2017-01-29 13:52:05:475 420 bf8 Agent * WU client version 7.6.7601.19161
2017-01-29 13:52:05:475 420 bf8 Agent * Base directory: C:\Windows\SoftwareDistribution
2017-01-29 13:52:05:475 420 bf8 Agent * Access type: No proxy
2017-01-29 13:52:05:475 420 bf8 Agent * Network state: Connected
2017-01-29 13:52:05:787 420 b9c Report CWERReporter::Init succeeded
2017-01-29 13:52:05:787 420 b9c Agent *********** Agent: Initializing Windows Update Agent ***********
2017-01-29 13:52:05:787 420 b9c Agent * Prerequisite roots succeeded.
2017-01-29 13:52:05:787 420 b9c Agent *********** Agent: Initializing global settings cache ***********
2017-01-29 13:52:05:787 420 b9c Agent * WSUS server: <NULL>
2017-01-29 13:52:05:787 420 b9c Agent * WSUS status server: <NULL>
2017-01-29 13:52:05:787 420 b9c Agent * Target group: (Unassigned Computers)
2017-01-29 13:52:05:787 420 b9c Agent * Windows Update access disabled: No
2017-01-29 13:52:05:787 420 b9c Agent * Found 1 persisted download calls to restore
2017-01-29 13:52:05:787 420 b9c Agent WARNING: WU client failed to initialize a download call from persisted data with potential error 0x80248002
2017-01-29 13:52:05:787 420 b9c DnldMgr Download manager restoring 0 downloads
2017-01-29 13:52:05:787 420 b9c Agent * Failed to load persisted download calls, error = 0x80248002
2017-01-29 13:52:05:802 420 b9c Agent Attempt 0 to obtain post-reboot results.
2017-01-29 13:52:06:770 420 bf8 Report *********** Report: Initializing static reporting data ***********
2017-01-29 13:52:06:770 420 bf8 Report * OS Version = 6.1.7601.1.0.65792
2017-01-29 13:52:06:770 420 bf8 Report * OS Product Type = 0x00000004
2017-01-29 13:52:06:816 420 bf8 Report * Computer Brand = Hewlett-Packard
2017-01-29 13:52:06:816 420 bf8 Report * Computer Model = HP xw4400 Workstation
2017-01-29 13:52:06:816 420 bf8 Report * Bios Revision = 786D7 v02.03
2017-01-29 13:52:06:816 420 bf8 Report * Bios Name = Default System BIOS
2017-01-29 13:52:06:816 420 bf8 Report * Bios Release Date = 2006-04-04T00:00:00
2017-01-29 13:52:06:816 420 bf8 Report * Locale ID = 1033
2017-01-29 13:52:16:769 420 b9c Handler Post-reboot status for package Package_for_KB3205394~31bf3856ad364e35~amd64~~6.1.1.3: 0x00000000.
2017-01-29 13:52:16:972 2280 b74 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-29 13:52:16:972 2280 b74 Misc = Process: C:\Program Files (x86)\LogMeIn\x64\LogMeIn.exe
2017-01-29 13:52:16:972 2280 b74 Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-29 13:52:16:972 2280 b74 COMAPI ————-
2017-01-29 13:52:16:972 2280 b74 COMAPI — START — COMAPI: Search [ClientId = LogMeIn]
2017-01-29 13:52:16:972 2280 b74 COMAPI ———
2017-01-29 13:52:16:972 2280 b74 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = LogMeIn]
2017-01-29 13:52:18:438 420 d70 Agent *************
2017-01-29 13:52:18:438 420 d70 Agent ** START ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-29 13:52:18:438 420 d70 Agent *********
2017-01-29 13:52:18:438 420 d70 Agent * Online = No; Ignore download priority = No
2017-01-29 13:52:18:438 420 d70 Agent * Criteria = “IsInstalled = 0 AND IsHidden = 0”
2017-01-29 13:52:18:438 420 d70 Agent * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2017-01-29 13:52:18:438 420 d70 Agent * Search Scope = {Machine}
2017-01-29 13:52:18:984 420 d70 Driver Matched driver to device USB\VID_046D&PID_081A&REV_0010&MI_02
2017-01-29 13:52:18:984 420 d70 Driver Status: 0x180200a, ProblemNumber: 00000000
2017-01-29 13:52:50:678 420 bf8 AU ########### AU: Initializing Automatic Updates ###########
2017-01-29 13:52:50:678 420 bf8 AU # AU disabled through User preference
2017-01-29 13:52:50:678 420 bf8 AU Initializing featured updates
2017-01-29 13:52:50:678 420 bf8 AU Found 0 cached featured updates
2017-01-29 13:52:50:678 420 bf8 AU Successfully wrote event for AU health state:0
2017-01-29 13:52:50:678 420 bf8 AU Successfully wrote event for AU health state:0
2017-01-29 13:52:50:678 420 bf8 AU AU finished delayed initialization
2017-01-29 15:29:31:074 420 9ac AU Triggering AU detection through DetectNow API
2017-01-29 15:29:31:083 420 9ac AU Triggering Online detection (interactive)
2017-01-29 15:29:31:091 420 bf8 AU #############
2017-01-29 15:29:31:091 420 bf8 AU ## START ## AU: Search for updates
2017-01-29 15:29:31:091 420 bf8 AU #########
2017-01-29 15:29:31:105 420 bf8 AU <<## SUBMITTED ## AU: Search for updates [CallId = {32C0A452-EBC7-4814-A909-1F04FA354DA8}]
2017-01-29 20:03:25:174 420 bf8 AU AU setting next sqm report timeout to 2017-01-31 01:03:25
2017-01-30 00:49:08:011 2728 12f4 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-30 00:49:08:031 2728 12f4 Misc = Process: C:\Windows\SysWOW64\wusa.exe
2017-01-30 00:49:08:031 2728 12f4 Misc = Module: C:\Windows\SysWOW64\wuapi.dll
2017-01-30 00:49:08:010 2728 12f4 COMAPI ———– COMAPI: IUpdateServiceManager::AddScanPackageService ———–
2017-01-30 00:49:08:031 2728 12f4 COMAPI – ServiceName = Windows Update Standalone Installer
2017-01-30 00:49:08:031 2728 12f4 COMAPI – ScanFileLocation = C:\fd4d7349f45832839337efe6a9e7\wsusscan.cab
2017-01-30 00:49:08:300 420 1b28 Misc Validating signature for C:\Windows\SoftwareDistribution\ScanFile\228c7050-9e09-4763-8926-aac44d58f98f\Source.cab with dwProvFlags 0x00000080:
2017-01-30 00:49:08:598 420 1b28 Misc Microsoft signed: Yes
2017-01-30 00:49:09:471 420 1b28 DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2017-01-30 00:49:09:501 2728 12f4 COMAPI – Added scan package service, ServiceID = {228C7050-9E09-4763-8926-AAC44D58F98F} Third party service
2017-01-30 00:49:09:529 2728 12f4 COMAPI ————-
2017-01-30 00:49:09:529 2728 12f4 COMAPI — START — COMAPI: Search [ClientId = wusa]
2017-01-30 00:49:09:529 2728 12f4 COMAPI ———
2017-01-30 00:49:09:634 2728 12f4 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = wusa]
2017-01-30 00:53:32:016 420 bf8 AU Sending shutdown notification
2017-01-30 00:53:32:016 420 bf8 AU AU initiates service shutdown
2017-01-30 00:53:32:016 420 bf8 AU ########### AU: Uninitializing Automatic Updates ###########
2017-01-30 00:53:32:016 420 d70 Agent * WARNING: Failed to filter search results, error = 0x8024000B
2017-01-30 00:53:33:061 420 d70 Agent *********
2017-01-30 00:53:33:061 420 d70 Agent ** END ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-30 00:53:33:061 420 d70 Agent *************
2017-01-30 00:53:33:061 2280 dbc COMAPI >>– RESUMED — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 00:53:33:093 2280 dbc COMAPI – Updates found = 0
2017-01-30 00:53:33:093 2280 dbc COMAPI – WARNING: Exit code = 0x00000000, Result code = 0x8024001E
2017-01-30 00:53:33:093 2280 dbc COMAPI ———
2017-01-30 00:53:33:093 2280 dbc COMAPI — END — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 00:53:33:093 2280 dbc COMAPI ————-
2017-01-30 00:53:33:061 420 bf8 Agent WARNING: WU client fails to call back to search call {84EFC8A5-460B-45ED-84D9-2CB720483200} with error 0x800706ba
2017-01-30 00:53:33:093 420 bf8 Agent Sending shutdown notification to client
2017-01-30 00:53:33:108 2280 1568 COMAPI WARNING: Received service shutdown/self-update notification.
2017-01-30 00:53:33:124 2280 b74 COMAPI WARNING: Operation failed due to earlier error, hr=8024001E
2017-01-30 00:53:33:124 2280 b74 COMAPI FATAL: Unable to complete asynchronous search. (hr=8024001E)
2017-01-30 00:53:33:124 420 bf8 Agent Sending shutdown notification to client
2017-01-30 00:53:33:124 420 bf8 Agent Sending shutdown notification to client
2017-01-30 00:53:33:249 420 bf8 Report REPORT EVENT: {6BB74C94-45B1-47BF-8CEA-7B4114FFF357} 2017-01-29 13:52:16:941-0500 1 183 101 {15A18FD4-240A-49EA-B9A9-936139646AC8} 501 0 wusa Success Content Install Installation Successful: Windows successfully installed the following update: Security Update for Windows (KB3205394)
2017-01-30 00:53:33:483 420 bf8 Service *********
2017-01-30 00:53:33:483 420 bf8 Service ** END ** Service: Service exit [Exit code = 0x240001]
2017-01-30 00:53:33:483 420 bf8 Service *************
2017-01-30 00:54:03:388 2280 b74 COMAPI FATAL: Unable to connect to the service (hr=80080005)
2017-01-30 00:54:03:388 2280 b74 COMAPI WARNING: Unable to establish connection to the service. (hr=80080005)
2017-01-30 00:54:03:388 2280 b74 COMAPI ————-
2017-01-30 00:54:03:388 2280 b74 COMAPI — START — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 00:54:03:388 2280 b74 COMAPI ———
2017-01-30 00:54:03:388 2280 b74 COMAPI FATAL: Unable to connect to the service (hr=8007045B)
2017-01-30 00:54:03:388 2280 b74 COMAPI WARNING: Unable to establish connection to the service. (hr=8007045B)
2017-01-30 00:54:03:388 2280 b74 COMAPI – WARNING: Exit code = 0x8007045B
2017-01-30 00:54:03:388 2280 b74 COMAPI ———
2017-01-30 00:54:03:388 2280 b74 COMAPI — END — COMAPI: Search [ClientId = <NULL>]
2017-01-30 00:54:03:388 2280 b74 COMAPI ————-
2017-01-30 00:54:03:388 2280 b74 COMAPI FATAL: Unable to initiate asynchronous search, hr=8007045B
2017-01-30 00:56:11:283 488 dac Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-30 00:56:11:283 488 dac Misc = Process: C:\Windows\system32\svchost.exe
2017-01-30 00:56:11:283 488 dac Misc = Module: c:\windows\system32\wuaueng.dll
2017-01-30 00:56:11:283 488 dac Service *************
2017-01-30 00:56:11:283 488 dac Service ** START ** Service: Service startup
2017-01-30 00:56:11:283 488 dac Service *********
2017-01-30 00:56:11:969 488 dac Agent * WU client version 7.6.7601.19161
2017-01-30 00:56:12:000 488 dac Agent * Base directory: C:\Windows\SoftwareDistribution
2017-01-30 00:56:12:016 488 dac Agent * Access type: No proxy
2017-01-30 00:56:12:578 488 dac Agent * Network state: Connected
2017-01-30 00:56:42:920 488 f38 Report CWERReporter::Init succeeded
2017-01-30 00:56:42:920 488 f38 Agent *********** Agent: Initializing Windows Update Agent ***********
2017-01-30 00:56:42:935 488 f38 Agent * Prerequisite roots succeeded.
2017-01-30 00:56:42:935 488 f38 Agent *********** Agent: Initializing global settings cache ***********
2017-01-30 00:56:42:935 488 f38 Agent * WSUS server: <NULL>
2017-01-30 00:56:42:935 488 f38 Agent * WSUS status server: <NULL>
2017-01-30 00:56:42:935 488 f38 Agent * Target group: (Unassigned Computers)
2017-01-30 00:56:42:935 488 f38 Agent * Windows Update access disabled: No
2017-01-30 00:56:43:247 488 f38 Agent * Found 1 persisted download calls to restore
2017-01-30 00:56:43:357 488 f38 Agent WARNING: WU client failed to initialize a download call from persisted data with potential error 0x80248002
2017-01-30 00:56:43:357 488 f38 DnldMgr Download manager restoring 0 downloads
2017-01-30 00:56:43:357 488 f38 Agent * Failed to load persisted download calls, error = 0x80248002
2017-01-30 00:56:44:215 488 dac Report *********** Report: Initializing static reporting data ***********
2017-01-30 00:56:44:215 488 dac Report * OS Version = 6.1.7601.1.0.65792
2017-01-30 00:56:44:215 488 dac Report * OS Product Type = 0x00000004
2017-01-30 00:56:44:433 488 dac Report * Computer Brand = Hewlett-Packard
2017-01-30 00:56:44:433 488 dac Report * Computer Model = HP xw4400 Workstation
2017-01-30 00:56:44:433 488 dac Report * Bios Revision = 786D7 v02.03
2017-01-30 00:56:44:433 488 dac Report * Bios Name = Default System BIOS
2017-01-30 00:56:44:433 488 dac Report * Bios Release Date = 2006-04-04T00:00:00
2017-01-30 00:56:44:433 488 dac Report * Locale ID = 1033
2017-01-30 00:56:50:658 4228 1090 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-30 00:56:50:658 4228 1090 Misc = Process: C:\Windows\system32\wusa.exe
2017-01-30 00:56:50:658 4228 1090 Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-30 00:56:50:658 4228 1090 COMAPI ———– COMAPI: IUpdateServiceManager::AddScanPackageService ———–
2017-01-30 00:56:50:658 4228 1090 COMAPI – ServiceName = Windows Update Standalone Installer
2017-01-30 00:56:50:658 4228 1090 COMAPI – ScanFileLocation = C:\202d9bbdecae381e4a\wsusscan.cab
2017-01-30 00:56:50:658 488 e94 Agent *********** Agent: Initializing Windows Update Agent ***********
2017-01-30 00:57:12:799 488 e94 Misc Validating signature for C:\Windows\SoftwareDistribution\ScanFile\8f212b72-f4c1-4e7e-a422-830a3a597571\Source.cab with dwProvFlags 0x00000080:
2017-01-30 00:57:12:918 2276 d08 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-30 00:57:12:918 2276 d08 Misc = Process: C:\Program Files (x86)\LogMeIn\x64\LogMeIn.exe
2017-01-30 00:57:12:918 2276 d08 Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-30 00:57:12:917 2276 d08 COMAPI ————-
2017-01-30 00:57:12:918 2276 d08 COMAPI — START — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 00:57:12:918 2276 d08 COMAPI ———
2017-01-30 00:57:13:107 2276 d08 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 00:57:13:356 488 e94 Misc Microsoft signed: Yes
2017-01-30 00:57:13:857 488 e94 DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2017-01-30 00:57:13:937 4228 1090 COMAPI – Added scan package service, ServiceID = {8F212B72-F4C1-4E7E-A422-830A3A597571} Third party service
2017-01-30 00:57:13:938 4228 1090 COMAPI ————-
2017-01-30 00:57:13:938 4228 1090 COMAPI — START — COMAPI: Search [ClientId = wusa]
2017-01-30 00:57:13:938 4228 1090 COMAPI ———
2017-01-30 00:57:13:953 4228 1090 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = wusa]
2017-01-30 00:57:26:840 488 11d4 Agent *************
2017-01-30 00:57:26:840 488 11d4 Agent ** START ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-30 00:57:26:843 488 11d4 Agent *********
2017-01-30 00:57:26:843 488 11d4 Agent * Online = No; Ignore download priority = No
2017-01-30 00:57:26:844 488 11d4 Agent * Criteria = “IsInstalled = 0 AND IsHidden = 0”
2017-01-30 00:57:26:844 488 11d4 Agent * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2017-01-30 00:57:26:844 488 11d4 Agent * Search Scope = {Machine}
2017-01-30 00:57:27:842 488 dac AU ########### AU: Initializing Automatic Updates ###########
2017-01-30 00:57:27:907 488 dac AU # AU disabled through User preference
2017-01-30 00:57:27:917 488 dac AU Initializing featured updates
2017-01-30 00:57:27:918 488 dac AU Found 0 cached featured updates
2017-01-30 00:57:27:925 488 dac AU Successfully wrote event for AU health state:0
2017-01-30 00:57:27:926 488 dac AU Successfully wrote event for AU health state:0
2017-01-30 00:57:27:927 488 dac AU AU finished delayed initialization
2017-01-30 00:57:29:714 488 11d4 Driver Matched driver to device USB\VID_046D&PID_081A&REV_0010&MI_02
2017-01-30 00:57:29:714 488 11d4 Driver Status: 0x180200a, ProblemNumber: 00000000
2017-01-30 06:46:03:787 488 dac AU Sending shutdown notification
2017-01-30 06:46:03:787 488 dac AU AU initiates service shutdown
2017-01-30 06:46:03:787 488 dac AU ########### AU: Uninitializing Automatic Updates ###########
2017-01-30 06:46:03:787 488 11d4 Agent * WARNING: Failed to filter search results, error = 0x8024000B
2017-01-30 06:46:03:818 488 11d4 Agent *********
2017-01-30 06:46:03:818 488 11d4 Agent ** END ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-30 06:46:03:818 488 11d4 Agent *************
2017-01-30 06:46:03:818 2276 b7c COMAPI >>– RESUMED — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 06:46:03:818 488 dac Agent WARNING: WU client fails to call back to search call {F7ADD817-1075-48BD-98F7-7BF5E763C1EC} with error 0x800706ba
2017-01-30 06:46:03:818 488 dac Agent Sending shutdown notification to client
2017-01-30 06:46:03:818 2276 b7c COMAPI – Updates found = 0
2017-01-30 06:46:03:818 2276 b7c COMAPI – WARNING: Exit code = 0x00000000, Result code = 0x8024001E
2017-01-30 06:46:03:818 2276 b7c COMAPI ———
2017-01-30 06:46:03:818 2276 b7c COMAPI — END — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 06:46:03:818 2276 b7c COMAPI ————-
2017-01-30 06:46:03:818 488 dac Agent Sending shutdown notification to client
2017-01-30 06:46:03:818 2276 d08 COMAPI WARNING: Operation failed due to earlier error, hr=8024001E
2017-01-30 06:46:03:818 2276 d08 COMAPI FATAL: Unable to complete asynchronous search. (hr=8024001E)
2017-01-30 06:46:03:818 2276 1134 COMAPI WARNING: Received service shutdown/self-update notification.
2017-01-30 06:46:03:834 488 dac Agent Sending shutdown notification to client
2017-01-30 06:46:04:146 488 dac Service *********
2017-01-30 06:46:04:146 488 dac Service ** END ** Service: Service exit [Exit code = 0x240001]
2017-01-30 06:46:04:146 488 dac Service *************
2017-01-30 06:48:01:130 316 af4 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-30 06:48:01:130 316 af4 Misc = Process: C:\Windows\system32\svchost.exe
2017-01-30 06:48:01:130 316 af4 Misc = Module: c:\windows\system32\wuaueng.dll
2017-01-30 06:48:01:130 316 af4 Service *************
2017-01-30 06:48:01:130 316 af4 Service ** START ** Service: Service startup
2017-01-30 06:48:01:130 316 af4 Service *********
2017-01-30 06:48:01:161 316 af4 Agent * WU client version 7.6.7601.19161
2017-01-30 06:48:01:161 316 af4 Agent * Base directory: C:\Windows\SoftwareDistribution
2017-01-30 06:48:01:161 316 af4 Agent * Access type: No proxy
2017-01-30 06:48:01:161 316 af4 Agent * Network state: Connected
2017-01-30 06:48:01:364 316 a60 Report CWERReporter::Init succeeded
2017-01-30 06:48:01:364 316 a60 Agent *********** Agent: Initializing Windows Update Agent ***********
2017-01-30 06:48:01:364 316 a60 Agent * Prerequisite roots succeeded.
2017-01-30 06:48:01:364 316 a60 Agent *********** Agent: Initializing global settings cache ***********
2017-01-30 06:48:01:364 316 a60 Agent * WSUS server: <NULL>
2017-01-30 06:48:01:364 316 a60 Agent * WSUS status server: <NULL>
2017-01-30 06:48:01:364 316 a60 Agent * Target group: (Unassigned Computers)
2017-01-30 06:48:01:364 316 a60 Agent * Windows Update access disabled: No
2017-01-30 06:48:01:364 316 a60 Agent * Found 1 persisted download calls to restore
2017-01-30 06:48:01:364 316 a60 Agent WARNING: WU client failed to initialize a download call from persisted data with potential error 0x80248002
2017-01-30 06:48:01:364 316 a60 DnldMgr Download manager restoring 0 downloads
2017-01-30 06:48:01:364 316 a60 Agent * Failed to load persisted download calls, error = 0x80248002
2017-01-30 06:48:02:471 316 af4 Report *********** Report: Initializing static reporting data ***********
2017-01-30 06:48:02:471 316 af4 Report * OS Version = 6.1.7601.1.0.65792
2017-01-30 06:48:02:471 316 af4 Report * OS Product Type = 0x00000004
2017-01-30 06:48:02:518 316 af4 Report * Computer Brand = Hewlett-Packard
2017-01-30 06:48:02:518 316 af4 Report * Computer Model = HP xw4400 Workstation
2017-01-30 06:48:02:518 316 af4 Report * Bios Revision = 786D7 v02.03
2017-01-30 06:48:02:518 316 af4 Report * Bios Name = Default System BIOS
2017-01-30 06:48:02:518 316 af4 Report * Bios Release Date = 2006-04-04T00:00:00
2017-01-30 06:48:02:518 316 af4 Report * Locale ID = 1033
2017-01-30 06:48:05:373 2268 b20 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-30 06:48:05:373 2268 b20 Misc = Process: C:\Program Files (x86)\LogMeIn\x64\LogMeIn.exe
2017-01-30 06:48:05:373 2268 b20 Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-30 06:48:05:373 2268 b20 COMAPI ————-
2017-01-30 06:48:05:373 2268 b20 COMAPI — START — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 06:48:05:373 2268 b20 COMAPI ———
2017-01-30 06:48:05:389 2268 b20 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 06:48:05:545 316 c08 Agent *************
2017-01-30 06:48:05:545 316 c08 Agent ** START ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-30 06:48:05:545 316 c08 Agent *********
2017-01-30 06:48:05:545 316 c08 Agent * Online = No; Ignore download priority = No
2017-01-30 06:48:05:545 316 c08 Agent * Criteria = “IsInstalled = 0 AND IsHidden = 0”
2017-01-30 06:48:05:545 316 c08 Agent * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2017-01-30 06:48:05:545 316 c08 Agent * Search Scope = {Machine}
2017-01-30 06:48:06:169 316 c08 Driver Matched driver to device USB\VID_046D&PID_081A&REV_0010&MI_02
2017-01-30 06:48:06:169 316 c08 Driver Status: 0x180200a, ProblemNumber: 00000000
2017-01-30 06:48:46:276 316 af4 AU ########### AU: Initializing Automatic Updates ###########
2017-01-30 06:48:46:292 316 af4 AU # AU disabled through User preference
2017-01-30 06:48:46:292 316 af4 AU Initializing featured updates
2017-01-30 06:48:46:292 316 af4 AU Found 0 cached featured updates
2017-01-30 06:48:46:323 316 af4 AU Successfully wrote event for AU health state:0
2017-01-30 06:48:46:323 316 af4 AU Successfully wrote event for AU health state:0
2017-01-30 06:48:46:323 316 af4 AU AU finished delayed initialization
2017-01-30 10:01:22:360 316 af4 AU ########### AU: Uninitializing Automatic Updates ###########
2017-01-30 10:01:22:360 316 c08 Agent * WARNING: Failed to filter search results, error = 0x8024000B
2017-01-30 10:01:22:943 316 c08 Agent *********
2017-01-30 10:01:22:944 316 c08 Agent ** END ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-30 10:01:22:944 316 c08 Agent *************
2017-01-30 10:01:22:951 316 af4 Agent Sending shutdown notification to client
2017-01-30 10:01:22:951 2268 e80 COMAPI >>– RESUMED — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 10:01:22:952 2268 e80 COMAPI – Updates found = 0
2017-01-30 10:01:22:952 2268 e80 COMAPI – WARNING: Exit code = 0x00000000, Result code = 0x8024001E
2017-01-30 10:01:22:952 2268 e80 COMAPI ———
2017-01-30 10:01:22:952 2268 e80 COMAPI — END — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 10:01:22:952 2268 e80 COMAPI ————-
2017-01-30 10:01:22:951 2268 95c COMAPI WARNING: Received service shutdown/self-update notification.
2017-01-30 10:01:22:952 2268 b20 COMAPI WARNING: Operation failed due to earlier error, hr=8024001E
2017-01-30 10:01:22:967 2268 b20 COMAPI FATAL: Unable to complete asynchronous search. (hr=8024001E)
2017-01-30 10:01:23:320 316 af4 Service *********
2017-01-30 10:01:23:320 316 af4 Service ** END ** Service: Service exit [Exit code = 0x240001]
2017-01-30 10:01:23:320 316 af4 Service *************
2017-01-30 10:01:53:028 2268 b20 COMAPI FATAL: Unable to connect to the service (hr=80080005)
2017-01-30 10:01:53:029 2268 b20 COMAPI WARNING: Unable to establish connection to the service. (hr=80080005)
2017-01-30 10:01:53:029 2268 b20 COMAPI ————-
2017-01-30 10:01:53:029 2268 b20 COMAPI — START — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 10:01:53:029 2268 b20 COMAPI ———
2017-01-30 10:01:53:071 316 ebc Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-30 10:01:53:071 316 ebc Misc = Process: C:\Windows\system32\svchost.exe
2017-01-30 10:01:53:071 316 ebc Misc = Module: c:\windows\system32\wuaueng.dll
2017-01-30 10:01:53:071 316 ebc Service *************
2017-01-30 10:01:53:071 316 ebc Service ** START ** Service: Service startup
2017-01-30 10:01:53:071 316 ebc Service *********
2017-01-30 10:01:53:126 316 ebc Agent * WU client version 7.6.7601.19161
2017-01-30 10:01:53:126 316 ebc Agent * Base directory: C:\Windows\SoftwareDistribution
2017-01-30 10:01:53:127 316 ebc Agent * Access type: No proxy
2017-01-30 10:01:53:128 316 ebc Agent * Network state: Connected
2017-01-30 10:01:53:300 316 1470 Report CWERReporter::Init succeeded
2017-01-30 10:01:53:300 316 1470 Agent *********** Agent: Initializing Windows Update Agent ***********
2017-01-30 10:01:53:301 316 1470 Agent * Prerequisite roots succeeded.
2017-01-30 10:01:53:301 316 1470 Agent *********** Agent: Initializing global settings cache ***********
2017-01-30 10:01:53:301 316 1470 Agent * WSUS server: <NULL>
2017-01-30 10:01:53:301 316 1470 Agent * WSUS status server: <NULL>
2017-01-30 10:01:53:301 316 1470 Agent * Target group: (Unassigned Computers)
2017-01-30 10:01:53:301 316 1470 Agent * Windows Update access disabled: No
2017-01-30 10:01:53:327 316 1470 Agent * Found 1 persisted download calls to restore
2017-01-30 10:01:53:327 316 1470 Agent WARNING: WU client failed to initialize a download call from persisted data with potential error 0x80248002
2017-01-30 10:01:53:327 316 1470 DnldMgr Download manager restoring 0 downloads
2017-01-30 10:01:53:327 316 1470 Agent * Failed to load persisted download calls, error = 0x80248002
2017-01-30 10:01:53:359 2268 b20 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 10:01:54:277 316 ebc Report *********** Report: Initializing static reporting data ***********
2017-01-30 10:01:54:278 316 ebc Report * OS Version = 6.1.7601.1.0.65792
2017-01-30 10:01:54:278 316 ebc Report * OS Product Type = 0x00000004
2017-01-30 10:01:54:300 316 ebc Report * Computer Brand = Hewlett-Packard
2017-01-30 10:01:54:300 316 ebc Report * Computer Model = HP xw4400 Workstation
2017-01-30 10:01:54:303 316 ebc Report * Bios Revision = 786D7 v02.03
2017-01-30 10:01:54:303 316 ebc Report * Bios Name = Default System BIOS
2017-01-30 10:01:54:303 316 ebc Report * Bios Release Date = 2006-04-04T00:00:00
2017-01-30 10:01:54:303 316 ebc Report * Locale ID = 1033
2017-01-30 10:01:56:800 316 b2c Agent *************
2017-01-30 10:01:56:801 316 b2c Agent ** START ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-30 10:01:56:801 316 b2c Agent *********
2017-01-30 10:01:56:801 316 b2c Agent * Online = No; Ignore download priority = No
2017-01-30 10:01:56:801 316 b2c Agent * Criteria = “IsInstalled = 0 AND IsHidden = 0”
2017-01-30 10:01:56:801 316 b2c Agent * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2017-01-30 10:01:56:801 316 b2c Agent * Search Scope = {Machine}
2017-01-30 10:01:58:824 316 b2c Driver Matched driver to device USB\VID_046D&PID_081A&REV_0010&MI_02
2017-01-30 10:01:58:824 316 b2c Driver Status: 0x180200a, ProblemNumber: 00000000
2017-01-30 10:02:38:287 316 ebc AU ########### AU: Initializing Automatic Updates ###########
2017-01-30 10:02:38:288 316 ebc AU # AU disabled through User preference
2017-01-30 10:02:38:288 316 ebc AU Initializing featured updates
2017-01-30 10:02:38:288 316 ebc AU Found 0 cached featured updates
2017-01-30 10:02:38:288 316 ebc AU Successfully wrote event for AU health state:0
2017-01-30 10:02:38:289 316 ebc AU Successfully wrote event for AU health state:0
2017-01-30 10:02:38:289 316 ebc AU AU finished delayed initialization
2017-01-30 10:07:45:568 384 14fc Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-30 10:07:45:568 384 14fc Misc = Process: C:\Windows\system32\wusa.exe
2017-01-30 10:07:45:568 384 14fc Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-30 10:07:45:568 384 14fc COMAPI ———– COMAPI: IUpdateServiceManager::AddScanPackageService ———–
2017-01-30 10:07:45:568 384 14fc COMAPI – ServiceName = Windows Update Standalone Installer
2017-01-30 10:07:45:568 384 14fc COMAPI – ScanFileLocation = C:\5f5f45db2d13fd668bc481e1ff28bb97\wsusscan.cab
2017-01-30 10:07:45:677 316 11f8 Misc Validating signature for C:\Windows\SoftwareDistribution\ScanFile\7e4f00bb-d593-492f-9da8-0fa5d770c217\Source.cab with dwProvFlags 0x00000080:
2017-01-30 10:07:45:896 316 11f8 Misc Microsoft signed: Yes
2017-01-30 10:07:45:990 316 11f8 DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2017-01-30 10:07:46:006 384 14fc COMAPI – Added scan package service, ServiceID = {7E4F00BB-D593-492F-9DA8-0FA5D770C217} Third party service
2017-01-30 10:07:46:006 384 14fc COMAPI ————-
2017-01-30 10:07:46:006 384 14fc COMAPI — START — COMAPI: Search [ClientId = wusa]
2017-01-30 10:07:46:006 384 14fc COMAPI ———
2017-01-30 10:07:46:006 384 14fc COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = wusa]
2017-01-30 10:36:06:007 2892 1568 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-30 10:36:06:007 2892 1568 Misc = Process: C:\Windows\system32\wusa.exe
2017-01-30 10:36:06:007 2892 1568 Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-30 10:36:06:007 2892 1568 COMAPI ———– COMAPI: IUpdateServiceManager::AddScanPackageService ———–
2017-01-30 10:36:06:007 2892 1568 COMAPI – ServiceName = Windows Update Standalone Installer
2017-01-30 10:36:06:007 2892 1568 COMAPI – ScanFileLocation = C:\f264a47d55e3f813618028\wsusscan.cab
2017-01-30 10:36:06:054 316 37c Misc Validating signature for C:\Windows\SoftwareDistribution\ScanFile\927e570a-4887-4cb9-946e-91bd44abefc7\Source.cab with dwProvFlags 0x00000080:
2017-01-30 10:36:06:069 316 37c Misc Microsoft signed: Yes
2017-01-30 10:36:06:412 316 37c DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2017-01-30 10:36:06:412 2892 1568 COMAPI – Added scan package service, ServiceID = {927E570A-4887-4CB9-946E-91BD44ABEFC7} Third party service
2017-01-30 10:36:06:412 2892 1568 COMAPI ————-
2017-01-30 10:36:06:412 2892 1568 COMAPI — START — COMAPI: Search [ClientId = wusa]
2017-01-30 10:36:06:412 2892 1568 COMAPI ———
2017-01-30 10:36:06:412 2892 1568 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = wusa]
2017-01-30 13:30:24:217 316 ebc AU ########### AU: Uninitializing Automatic Updates ###########
2017-01-30 13:30:24:239 316 b2c Agent * WARNING: Failed to filter search results, error = 0x8024000B
2017-01-30 13:30:25:048 316 b2c Agent *********
2017-01-30 13:30:25:048 316 b2c Agent ** END ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-30 13:30:25:048 316 b2c Agent *************
2017-01-30 13:30:25:083 2268 398 COMAPI >>– RESUMED — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 13:30:25:084 2268 398 COMAPI – Updates found = 0
2017-01-30 13:30:25:084 2268 398 COMAPI – WARNING: Exit code = 0x00000000, Result code = 0x8024001E
2017-01-30 13:30:25:084 2268 398 COMAPI ———
2017-01-30 13:30:25:084 2268 398 COMAPI — END — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 13:30:25:084 2268 398 COMAPI ————-
2017-01-30 13:30:25:085 2268 b20 COMAPI WARNING: Operation failed due to earlier error, hr=8024001E
2017-01-30 13:30:25:085 2268 b20 COMAPI FATAL: Unable to complete asynchronous search. (hr=8024001E)
2017-01-30 13:30:25:084 316 ebc Agent WARNING: WU client fails to call back to search call {6D2DF9CE-31B7-4CC6-9585-6D34AEDEF189} with error 0x800706ba
2017-01-30 13:30:25:092 316 ebc Agent WARNING: WU client fails to call back to search call {7BBD39F5-BB39-47AC-A818-82A3C4D70C82} with error 0x800706ba
2017-01-30 13:30:25:092 316 ebc Agent Sending shutdown notification to client
2017-01-30 13:30:25:093 2268 ff8 COMAPI WARNING: Received service shutdown/self-update notification.
2017-01-30 13:30:25:093 316 ebc Agent Sending shutdown notification to client
2017-01-30 13:30:25:094 316 ebc Agent Sending shutdown notification to client
2017-01-30 13:30:25:094 316 ebc Agent Sending shutdown notification to client
2017-01-30 13:30:25:095 316 ebc Agent Sending shutdown notification to client
2017-01-30 13:30:25:227 316 ebc Service *********
2017-01-30 13:30:25:227 316 ebc Service ** END ** Service: Service exit [Exit code = 0x240001]
2017-01-30 13:30:25:228 316 ebc Service *************
2017-01-30 13:30:55:091 2268 b20 COMAPI FATAL: Unable to connect to the service (hr=80080005)
2017-01-30 13:30:55:091 2268 b20 COMAPI WARNING: Unable to establish connection to the service. (hr=80080005)
2017-01-30 13:30:55:153 316 b48 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-30 13:30:55:153 316 b48 Misc = Process: C:\Windows\system32\svchost.exe
2017-01-30 13:30:55:153 316 b48 Misc = Module: c:\windows\system32\wuaueng.dll
2017-01-30 13:30:55:152 316 b48 Service *************
2017-01-30 13:30:55:153 316 b48 Service ** START ** Service: Service startup
2017-01-30 13:30:55:153 316 b48 Service *********
2017-01-30 13:30:55:228 316 b48 Agent * WU client version 7.6.7601.19161
2017-01-30 13:30:55:229 316 b48 Agent * Base directory: C:\Windows\SoftwareDistribution
2017-01-30 13:30:55:229 316 b48 Agent * Access type: No proxy
2017-01-30 13:30:55:229 316 b48 Agent * Network state: Connected
2017-01-30 13:30:55:426 316 8f4 Report CWERReporter::Init succeeded
2017-01-30 13:30:55:426 316 8f4 Agent *********** Agent: Initializing Windows Update Agent ***********
2017-01-30 13:30:55:440 316 8f4 Agent * Prerequisite roots succeeded.
2017-01-30 13:30:55:440 316 8f4 Agent *********** Agent: Initializing global settings cache ***********
2017-01-30 13:30:55:440 316 8f4 Agent * WSUS server: <NULL>
2017-01-30 13:30:55:440 316 8f4 Agent * WSUS status server: <NULL>
2017-01-30 13:30:55:440 316 8f4 Agent * Target group: (Unassigned Computers)
2017-01-30 13:30:55:440 316 8f4 Agent * Windows Update access disabled: No
2017-01-30 13:30:55:449 316 8f4 Agent * Found 1 persisted download calls to restore
2017-01-30 13:30:55:449 316 8f4 Agent WARNING: WU client failed to initialize a download call from persisted data with potential error 0x80248002
2017-01-30 13:30:55:449 316 8f4 DnldMgr Download manager restoring 0 downloads
2017-01-30 13:30:55:449 316 8f4 Agent * Failed to load persisted download calls, error = 0x80248002
2017-01-30 13:30:56:139 316 b48 Report *********** Report: Initializing static reporting data ***********
2017-01-30 13:30:56:139 316 b48 Report * OS Version = 6.1.7601.1.0.65792
2017-01-30 13:30:56:139 316 b48 Report * OS Product Type = 0x00000004
2017-01-30 13:30:56:252 316 b48 Report * Computer Brand = Hewlett-Packard
2017-01-30 13:30:56:252 316 b48 Report * Computer Model = HP xw4400 Workstation
2017-01-30 13:30:56:256 316 b48 Report * Bios Revision = 786D7 v02.03
2017-01-30 13:30:56:256 316 b48 Report * Bios Name = Default System BIOS
2017-01-30 13:30:56:256 316 b48 Report * Bios Release Date = 2006-04-04T00:00:00
2017-01-30 13:30:56:256 316 b48 Report * Locale ID = 1033
2017-01-30 13:30:57:532 2268 b20 COMAPI ————-
2017-01-30 13:30:57:532 2268 b20 COMAPI — START — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 13:30:57:532 2268 b20 COMAPI ———
2017-01-30 13:30:57:691 2268 b20 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 13:30:58:701 316 3b4 Agent *************
2017-01-30 13:30:58:701 316 3b4 Agent ** START ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-30 13:30:58:701 316 3b4 Agent *********
2017-01-30 13:30:58:702 316 3b4 Agent * Online = No; Ignore download priority = No
2017-01-30 13:30:58:702 316 3b4 Agent * Criteria = “IsInstalled = 0 AND IsHidden = 0”
2017-01-30 13:30:58:702 316 3b4 Agent * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2017-01-30 13:30:58:702 316 3b4 Agent * Search Scope = {Machine}
2017-01-30 13:31:00:547 316 3b4 Driver Matched driver to device USB\VID_046D&PID_081A&REV_0010&MI_02
2017-01-30 13:31:00:547 316 3b4 Driver Status: 0x180200a, ProblemNumber: 00000000
2017-01-30 13:31:40:388 316 b48 AU ########### AU: Initializing Automatic Updates ###########
2017-01-30 13:31:40:389 316 b48 AU # AU disabled through User preference
2017-01-30 13:31:40:389 316 b48 AU Initializing featured updates
2017-01-30 13:31:40:389 316 b48 AU Found 0 cached featured updates
2017-01-30 13:31:40:390 316 b48 AU Successfully wrote event for AU health state:0
2017-01-30 13:31:40:390 316 b48 AU Successfully wrote event for AU health state:0
2017-01-30 13:31:40:390 316 b48 AU AU finished delayed initialization
2017-01-30 13:33:24:696 980 14c8 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-30 13:33:24:696 980 14c8 Misc = Process: C:\Windows\system32\wusa.exe
2017-01-30 13:33:24:696 980 14c8 Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-30 13:33:24:696 980 14c8 COMAPI ———– COMAPI: IUpdateServiceManager::AddScanPackageService ———–
2017-01-30 13:33:24:696 980 14c8 COMAPI – ServiceName = Windows Update Standalone Installer
2017-01-30 13:33:24:696 980 14c8 COMAPI – ScanFileLocation = C:\05e8ee597b4d7d49779b0564ed14\wsusscan.cab
2017-01-30 13:33:24:728 316 1240 Misc Validating signature for C:\Windows\SoftwareDistribution\ScanFile\1495ec8a-f756-4854-b394-4a348c475165\Source.cab with dwProvFlags 0x00000080:
2017-01-30 13:33:24:852 316 1240 Misc Microsoft signed: Yes
2017-01-30 13:33:24:915 316 1240 DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2017-01-30 13:33:24:915 980 14c8 COMAPI – Added scan package service, ServiceID = {1495EC8A-F756-4854-B394-4A348C475165} Third party service
2017-01-30 13:33:24:915 980 14c8 COMAPI ————-
2017-01-30 13:33:24:915 980 14c8 COMAPI — START — COMAPI: Search [ClientId = wusa]
2017-01-30 13:33:24:915 980 14c8 COMAPI ———
2017-01-30 13:33:24:915 980 14c8 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = wusa]
2017-01-30 15:35:40:637 316 b48 AU ########### AU: Uninitializing Automatic Updates ###########
2017-01-30 15:35:40:637 316 3b4 Agent * WARNING: Failed to filter search results, error = 0x8024000B
2017-01-30 15:35:41:261 316 3b4 Agent *********
2017-01-30 15:35:41:261 316 3b4 Agent ** END ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-30 15:35:41:261 316 3b4 Agent *************
2017-01-30 15:35:41:261 2268 e94 COMAPI >>– RESUMED — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 15:35:41:276 2268 e94 COMAPI – Updates found = 0
2017-01-30 15:35:41:276 2268 e94 COMAPI – WARNING: Exit code = 0x00000000, Result code = 0x8024001E
2017-01-30 15:35:41:276 2268 e94 COMAPI ———
2017-01-30 15:35:41:276 316 b48 Agent WARNING: WU client fails to call back to search call {53A17B69-1A36-4013-AB19-B09C9DEDD131} with error 0x800706ba
2017-01-30 15:35:41:276 2268 e94 COMAPI — END — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 15:35:41:276 2268 e94 COMAPI ————-
2017-01-30 15:35:41:276 316 b48 Agent Sending shutdown notification to client
2017-01-30 15:35:41:276 2268 b20 COMAPI WARNING: Operation failed due to earlier error, hr=8024001E
2017-01-30 15:35:41:276 2268 ac0 COMAPI WARNING: Received service shutdown/self-update notification.
2017-01-30 15:35:41:276 2268 b20 COMAPI FATAL: Unable to complete asynchronous search. (hr=8024001E)
2017-01-30 15:35:41:276 316 b48 Agent Sending shutdown notification to client
2017-01-30 15:35:41:276 316 b48 Agent Sending shutdown notification to client
2017-01-30 15:35:41:573 316 b48 Service *********
2017-01-30 15:35:41:573 316 b48 Service ** END ** Service: Service exit [Exit code = 0x240001]
2017-01-30 15:35:41:573 316 b48 Service *************
2017-01-30 15:36:11:288 2268 b20 COMAPI FATAL: Unable to connect to the service (hr=80080005)
2017-01-30 15:36:11:288 2268 b20 COMAPI WARNING: Unable to establish connection to the service. (hr=80080005)
2017-01-30 15:36:11:288 2268 b20 COMAPI ————-
2017-01-30 15:36:11:288 2268 b20 COMAPI — START — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 15:36:11:288 2268 b20 COMAPI ———
2017-01-30 15:36:11:319 316 14dc Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-30 15:36:11:319 316 14dc Misc = Process: C:\Windows\system32\svchost.exe
2017-01-30 15:36:11:319 316 14dc Misc = Module: c:\windows\system32\wuaueng.dll
2017-01-30 15:36:11:319 316 14dc Service *************
2017-01-30 15:36:11:319 316 14dc Service ** START ** Service: Service startup
2017-01-30 15:36:11:319 316 14dc Service *********
2017-01-30 15:36:11:335 316 14dc Agent * WU client version 7.6.7601.19161
2017-01-30 15:36:11:335 316 14dc Agent * Base directory: C:\Windows\SoftwareDistribution
2017-01-30 15:36:11:335 316 14dc Agent * Access type: No proxy
2017-01-30 15:36:11:335 316 14dc Agent * Network state: Connected
2017-01-30 15:36:11:459 316 c88 Report CWERReporter::Init succeeded
2017-01-30 15:36:11:459 316 c88 Agent *********** Agent: Initializing Windows Update Agent ***********
2017-01-30 15:36:11:459 316 c88 Agent * Prerequisite roots succeeded.
2017-01-30 15:36:11:459 316 c88 Agent *********** Agent: Initializing global settings cache ***********
2017-01-30 15:36:11:459 316 c88 Agent * WSUS server: <NULL>
2017-01-30 15:36:11:459 316 c88 Agent * WSUS status server: <NULL>
2017-01-30 15:36:11:459 316 c88 Agent * Target group: (Unassigned Computers)
2017-01-30 15:36:11:475 316 c88 Agent * Windows Update access disabled: No
2017-01-30 15:36:11:506 316 c88 Agent * Found 1 persisted download calls to restore
2017-01-30 15:36:11:506 316 c88 Agent WARNING: WU client failed to initialize a download call from persisted data with potential error 0x80248002
2017-01-30 15:36:11:506 316 c88 DnldMgr Download manager restoring 0 downloads
2017-01-30 15:36:11:506 316 c88 Agent * Failed to load persisted download calls, error = 0x80248002
2017-01-30 15:36:12:302 316 14dc Report *********** Report: Initializing static reporting data ***********
2017-01-30 15:36:12:302 316 14dc Report * OS Version = 6.1.7601.1.0.65792
2017-01-30 15:36:12:302 316 14dc Report * OS Product Type = 0x00000004
2017-01-30 15:36:12:302 316 14dc Report * Computer Brand = Hewlett-Packard
2017-01-30 15:36:12:302 316 14dc Report * Computer Model = HP xw4400 Workstation
2017-01-30 15:36:12:317 316 14dc Report * Bios Revision = 786D7 v02.03
2017-01-30 15:36:12:317 316 14dc Report * Bios Name = Default System BIOS
2017-01-30 15:36:12:317 316 14dc Report * Bios Release Date = 2006-04-04T00:00:00
2017-01-30 15:36:12:317 316 14dc Report * Locale ID = 1033
2017-01-30 15:36:13:378 2268 b20 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 15:36:14:143 316 1d4 Agent *************
2017-01-30 15:36:14:143 316 1d4 Agent ** START ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-30 15:36:14:143 316 1d4 Agent *********
2017-01-30 15:36:14:143 316 1d4 Agent * Online = No; Ignore download priority = No
2017-01-30 15:36:14:143 316 1d4 Agent * Criteria = “IsInstalled = 0 AND IsHidden = 0”
2017-01-30 15:36:14:143 316 1d4 Agent * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2017-01-30 15:36:14:143 316 1d4 Agent * Search Scope = {Machine}
2017-01-30 15:36:14:704 316 1d4 Driver Matched driver to device USB\VID_046D&PID_081A&REV_0010&MI_02
2017-01-30 15:36:14:704 316 1d4 Driver Status: 0x180200a, ProblemNumber: 00000000
2017-01-30 15:36:23:035 4268 fd0 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-30 15:36:23:035 4268 fd0 Misc = Process: C:\Windows\system32\wusa.exe
2017-01-30 15:36:23:035 4268 fd0 Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-30 15:36:23:035 4268 fd0 COMAPI ———– COMAPI: IUpdateServiceManager::AddScanPackageService ———–
2017-01-30 15:36:23:035 4268 fd0 COMAPI – ServiceName = Windows Update Standalone Installer
2017-01-30 15:36:23:035 4268 fd0 COMAPI – ScanFileLocation = C:\2e7fb0918b73bba10dde9e848698af\wsusscan.cab
2017-01-30 15:36:23:066 316 1718 Misc Validating signature for C:\Windows\SoftwareDistribution\ScanFile\75a543bf-536e-4754-a9c8-277ca4731243\Source.cab with dwProvFlags 0x00000080:
2017-01-30 15:36:23:113 316 1718 Misc Microsoft signed: Yes
2017-01-30 15:36:23:128 316 1718 DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2017-01-30 15:36:23:128 4268 fd0 COMAPI – Added scan package service, ServiceID = {75A543BF-536E-4754-A9C8-277CA4731243} Third party service
2017-01-30 15:36:23:128 4268 fd0 COMAPI ————-
2017-01-30 15:36:23:128 4268 fd0 COMAPI — START — COMAPI: Search [ClientId = wusa]
2017-01-30 15:36:23:128 4268 fd0 COMAPI ———
2017-01-30 15:36:23:128 4268 fd0 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = wusa]
2017-01-30 15:36:56:465 316 14dc AU ########### AU: Initializing Automatic Updates ###########
2017-01-30 15:36:56:465 316 14dc AU # AU disabled through User preference
2017-01-30 15:36:56:465 316 14dc AU Initializing featured updates
2017-01-30 15:36:56:465 316 14dc AU Found 0 cached featured updates
2017-01-30 15:36:56:465 316 14dc AU Successfully wrote event for AU health state:0
2017-01-30 15:36:56:465 316 14dc AU Successfully wrote event for AU health state:0
2017-01-30 15:36:56:465 316 14dc AU AU finished delayed initialization
2017-01-30 15:45:29:904 316 14dc AU Sending shutdown notification
2017-01-30 15:45:29:904 316 14dc AU AU initiates service shutdown
2017-01-30 15:45:29:904 316 14dc AU ########### AU: Uninitializing Automatic Updates ###########
2017-01-30 15:45:29:904 316 1d4 Agent * WARNING: Failed to filter search results, error = 0x8024000B
2017-01-30 15:45:29:920 316 1d4 Agent *********
2017-01-30 15:45:29:920 316 1d4 Agent ** END ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-30 15:45:29:920 316 1d4 Agent *************
2017-01-30 15:45:29:935 2268 16d4 COMAPI >>– RESUMED — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 15:45:29:935 316 14dc Agent WARNING: WU client fails to call back to search call {F50399D3-FC21-426A-9502-2CFF8221CAD2} with error 0x800706ba
2017-01-30 15:45:29:935 316 14dc Agent Sending shutdown notification to client
2017-01-30 15:45:29:935 2268 16d4 COMAPI – Updates found = 0
2017-01-30 15:45:29:935 2268 16d4 COMAPI – WARNING: Exit code = 0x00000000, Result code = 0x8024001E
2017-01-30 15:45:29:935 2268 16d4 COMAPI ———
2017-01-30 15:45:29:935 2268 f5c COMAPI WARNING: Received service shutdown/self-update notification.
2017-01-30 15:45:29:935 2268 16d4 COMAPI — END — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 15:45:29:935 2268 16d4 COMAPI ————-
2017-01-30 15:45:29:935 316 14dc Agent Sending shutdown notification to client
2017-01-30 15:45:29:935 2268 b20 COMAPI WARNING: Operation failed due to earlier error, hr=8024001E
2017-01-30 15:45:29:935 2268 b20 COMAPI FATAL: Unable to complete asynchronous search. (hr=8024001E)
2017-01-30 15:45:29:935 316 14dc Agent Sending shutdown notification to client
2017-01-30 15:45:30:154 316 14dc Service *********
2017-01-30 15:45:30:154 316 14dc Service ** END ** Service: Service exit [Exit code = 0x240001]
2017-01-30 15:45:30:154 316 14dc Service *************
2017-01-30 15:49:22:413 304 12f8 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-30 15:49:22:413 304 12f8 Misc = Process: C:\Windows\system32\svchost.exe
2017-01-30 15:49:22:413 304 12f8 Misc = Module: c:\windows\system32\wuaueng.dll
2017-01-30 15:49:22:413 304 12f8 Service *************
2017-01-30 15:49:22:413 304 12f8 Service ** START ** Service: Service startup
2017-01-30 15:49:22:413 304 12f8 Service *********
2017-01-30 15:49:22:460 304 12f8 Agent * WU client version 7.6.7601.19161
2017-01-30 15:49:22:460 304 12f8 Agent * Base directory: C:\Windows\SoftwareDistribution
2017-01-30 15:49:22:460 304 12f8 Agent * Access type: No proxy
2017-01-30 15:49:22:476 304 12f8 Agent * Network state: Connected
2017-01-30 15:49:23:198 304 1370 Report CWERReporter::Init succeeded
2017-01-30 15:49:23:198 304 1370 Agent *********** Agent: Initializing Windows Update Agent ***********
2017-01-30 15:49:23:198 304 1370 Agent * Prerequisite roots succeeded.
2017-01-30 15:49:23:198 304 1370 Agent *********** Agent: Initializing global settings cache ***********
2017-01-30 15:49:23:198 304 1370 Agent * WSUS server: <NULL>
2017-01-30 15:49:23:198 304 1370 Agent * WSUS status server: <NULL>
2017-01-30 15:49:23:198 304 1370 Agent * Target group: (Unassigned Computers)
2017-01-30 15:49:23:198 304 1370 Agent * Windows Update access disabled: No
2017-01-30 15:49:23:198 304 1370 Agent * Found 1 persisted download calls to restore
2017-01-30 15:49:23:198 304 1370 Agent WARNING: WU client failed to initialize a download call from persisted data with potential error 0x80248002
2017-01-30 15:49:23:198 304 1370 DnldMgr Download manager restoring 0 downloads
2017-01-30 15:49:23:198 304 1370 Agent * Failed to load persisted download calls, error = 0x80248002
2017-01-30 15:49:26:323 304 12f8 Report *********** Report: Initializing static reporting data ***********
2017-01-30 15:49:26:323 304 12f8 Report * OS Version = 6.1.7601.1.0.65792
2017-01-30 15:49:26:323 304 12f8 Report * OS Product Type = 0x00000004
2017-01-30 15:49:26:354 304 12f8 Report * Computer Brand = Hewlett-Packard
2017-01-30 15:49:26:354 304 12f8 Report * Computer Model = HP xw4400 Workstation
2017-01-30 15:49:26:354 304 12f8 Report * Bios Revision = 786D7 v02.03
2017-01-30 15:49:26:354 304 12f8 Report * Bios Name = Default System BIOS
2017-01-30 15:49:26:354 304 12f8 Report * Bios Release Date = 2006-04-04T00:00:00
2017-01-30 15:49:26:354 304 12f8 Report * Locale ID = 1033
2017-01-30 15:49:50:272 2568 1094 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-30 15:49:50:272 2568 1094 Misc = Process: C:\Program Files (x86)\LogMeIn\x64\LogMeIn.exe
2017-01-30 15:49:50:272 2568 1094 Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-30 15:49:50:271 2568 1094 COMAPI ————-
2017-01-30 15:49:50:272 2568 1094 COMAPI — START — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 15:49:50:272 2568 1094 COMAPI ———
2017-01-30 15:49:50:279 2568 1094 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = LogMeIn]
2017-01-30 15:49:53:044 304 1450 Agent *************
2017-01-30 15:49:53:044 304 1450 Agent ** START ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-30 15:49:53:044 304 1450 Agent *********
2017-01-30 15:49:53:044 304 1450 Agent * Online = No; Ignore download priority = No
2017-01-30 15:49:53:044 304 1450 Agent * Criteria = “IsInstalled = 0 AND IsHidden = 0”
2017-01-30 15:49:53:044 304 1450 Agent * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2017-01-30 15:49:53:044 304 1450 Agent * Search Scope = {Machine}
2017-01-30 15:49:55:454 304 1450 Driver Matched driver to device USB\VID_046D&PID_081A&REV_0010&MI_02
2017-01-30 15:49:55:454 304 1450 Driver Status: 0x180200a, ProblemNumber: 00000000
2017-01-30 15:50:08:090 304 12f8 AU ########### AU: Initializing Automatic Updates ###########
2017-01-30 15:50:08:607 304 12f8 AU # AU disabled through User preference
2017-01-30 15:50:08:701 304 12f8 AU Initializing featured updates
2017-01-30 15:50:08:701 304 12f8 AU Found 0 cached featured updates
2017-01-30 15:50:09:059 304 12f8 AU Successfully wrote event for AU health state:0
2017-01-30 15:50:09:059 304 12f8 AU Successfully wrote event for AU health state:0
2017-01-30 15:50:09:059 304 12f8 AU AU finished delayed initialization
2017-01-30 16:14:24:317 5964 1110 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-30 16:14:24:317 5964 1110 Misc = Process: c:\Program Files\Microsoft Security Client\MpCmdRun.exe
2017-01-30 16:14:24:317 5964 1110 Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-30 16:14:24:317 5964 1110 COMAPI ————-
2017-01-30 16:14:24:317 5964 1110 COMAPI — START — COMAPI: Search [ClientId = Microsoft Security Essentials (EDB4FA23-53B8-4AFA-8C5D-99752CCA7094)]
2017-01-30 16:14:24:317 5964 1110 COMAPI ———
2017-01-30 16:14:24:582 5964 1110 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = Microsoft Security Essentials (EDB4FA23-53B8-4AFA-8C5D-99752CCA7094)]
2017-01-30 20:03:25:013 304 12f8 AU AU setting next sqm report timeout to 2017-02-01 01:03:25
2017-01-31 12:22:30:892 304 12f8 AU ########### AU: Uninitializing Automatic Updates ###########
2017-01-31 12:22:30:908 304 1450 Agent * WARNING: Failed to filter search results, error = 0x8024000B
2017-01-31 12:22:32:140 304 1450 Agent *********
2017-01-31 12:22:32:140 304 1450 Agent ** END ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-31 12:22:32:140 304 1450 Agent *************
2017-01-31 12:22:32:343 2568 167c COMAPI >>– RESUMED — COMAPI: Search [ClientId = LogMeIn]
2017-01-31 12:22:32:358 304 12f8 Agent WARNING: WU client fails to call back to search call {28D1D7C2-AD94-4468-A937-B414B5635ED7} with error 0x800706ba
2017-01-31 12:22:32:358 304 12f8 Agent Sending shutdown notification to client
2017-01-31 12:22:32:358 2568 b30 COMAPI WARNING: Received service shutdown/self-update notification.
2017-01-31 12:22:32:358 304 12f8 Agent Sending shutdown notification to client
2017-01-31 12:22:32:358 2568 167c COMAPI – Updates found = 0
2017-01-31 12:22:32:358 2568 167c COMAPI – WARNING: Exit code = 0x00000000, Result code = 0x8024001E
2017-01-31 12:22:32:358 2568 167c COMAPI ———
2017-01-31 12:22:32:358 2568 167c COMAPI — END — COMAPI: Search [ClientId = LogMeIn]
2017-01-31 12:22:32:358 2568 167c COMAPI ————-
2017-01-31 12:22:32:358 2568 1094 COMAPI WARNING: Operation failed due to earlier error, hr=8024001E
2017-01-31 12:22:32:374 2568 1094 COMAPI FATAL: Unable to complete asynchronous search. (hr=8024001E)
2017-01-31 12:22:32:780 304 12f8 Service *********
2017-01-31 12:22:32:780 304 12f8 Service ** END ** Service: Service exit [Exit code = 0x240001]
2017-01-31 12:22:32:780 304 12f8 Service *************
2017-01-31 12:23:02:607 2568 1094 COMAPI FATAL: Unable to connect to the service (hr=80080005)
2017-01-31 12:23:02:607 2568 1094 COMAPI WARNING: Unable to establish connection to the service. (hr=80080005)
2017-01-31 12:23:02:607 2568 1094 COMAPI ————-
2017-01-31 12:23:02:607 2568 1094 COMAPI — START — COMAPI: Search [ClientId = LogMeIn]
2017-01-31 12:23:02:607 2568 1094 COMAPI ———
2017-01-31 12:23:02:622 304 117c Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-31 12:23:02:622 304 117c Misc = Process: C:\Windows\system32\svchost.exe
2017-01-31 12:23:02:622 304 117c Misc = Module: c:\windows\system32\wuaueng.dll
2017-01-31 12:23:02:622 304 117c Service *************
2017-01-31 12:23:02:622 304 117c Service ** START ** Service: Service startup
2017-01-31 12:23:02:622 304 117c Service *********
2017-01-31 12:23:02:685 304 117c Agent * WU client version 7.6.7601.19161
2017-01-31 12:23:02:685 304 117c Agent * Base directory: C:\Windows\SoftwareDistribution
2017-01-31 12:23:02:685 304 117c Agent * Access type: No proxy
2017-01-31 12:23:02:716 304 117c Agent * Network state: Connected
2017-01-31 12:23:02:997 304 14b8 Report CWERReporter::Init succeeded
2017-01-31 12:23:02:997 304 14b8 Agent *********** Agent: Initializing Windows Update Agent ***********
2017-01-31 12:23:03:059 304 14b8 Agent * Prerequisite roots succeeded.
2017-01-31 12:23:03:059 304 14b8 Agent *********** Agent: Initializing global settings cache ***********
2017-01-31 12:23:03:059 304 14b8 Agent * WSUS server: <NULL>
2017-01-31 12:23:03:059 304 14b8 Agent * WSUS status server: <NULL>
2017-01-31 12:23:03:059 304 14b8 Agent * Target group: (Unassigned Computers)
2017-01-31 12:23:03:059 304 14b8 Agent * Windows Update access disabled: No
2017-01-31 12:23:03:059 304 14b8 Agent * Found 1 persisted download calls to restore
2017-01-31 12:23:03:059 304 14b8 Agent WARNING: WU client failed to initialize a download call from persisted data with potential error 0x80248002
2017-01-31 12:23:03:059 304 14b8 DnldMgr Download manager restoring 0 downloads
2017-01-31 12:23:03:059 304 14b8 Agent * Failed to load persisted download calls, error = 0x80248002
2017-01-31 12:23:03:106 2568 1094 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = LogMeIn]
2017-01-31 12:23:04:806 304 117c Report *********** Report: Initializing static reporting data ***********
2017-01-31 12:23:04:806 304 117c Report * OS Version = 6.1.7601.1.0.65792
2017-01-31 12:23:04:806 304 117c Report * OS Product Type = 0x00000004
2017-01-31 12:23:04:838 304 117c Report * Computer Brand = Hewlett-Packard
2017-01-31 12:23:04:838 304 117c Report * Computer Model = HP xw4400 Workstation
2017-01-31 12:23:04:838 304 117c Report * Bios Revision = 786D7 v02.03
2017-01-31 12:23:04:838 304 117c Report * Bios Name = Default System BIOS
2017-01-31 12:23:04:838 304 117c Report * Bios Release Date = 2006-04-04T00:00:00
2017-01-31 12:23:04:838 304 117c Report * Locale ID = 1033
2017-01-31 12:23:07:334 304 15bc Agent *************
2017-01-31 12:23:07:334 304 15bc Agent ** START ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-31 12:23:07:334 304 15bc Agent *********
2017-01-31 12:23:07:334 304 15bc Agent * Online = No; Ignore download priority = No
2017-01-31 12:23:07:334 304 15bc Agent * Criteria = “IsInstalled = 0 AND IsHidden = 0”
2017-01-31 12:23:07:334 304 15bc Agent * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2017-01-31 12:23:07:334 304 15bc Agent * Search Scope = {Machine}
2017-01-31 12:23:08:753 304 15bc Driver Matched driver to device USB\VID_046D&PID_081A&REV_0010&MI_02
2017-01-31 12:23:08:753 304 15bc Driver Status: 0x180200a, ProblemNumber: 00000000
2017-01-31 12:23:47:950 304 117c AU ########### AU: Initializing Automatic Updates ###########
2017-01-31 12:23:47:950 304 117c AU # AU disabled through User preference
2017-01-31 12:23:47:950 304 117c AU Initializing featured updates
2017-01-31 12:23:47:950 304 117c AU Found 0 cached featured updates
2017-01-31 12:23:47:950 304 117c AU Successfully wrote event for AU health state:0
2017-01-31 12:23:47:950 304 117c AU Successfully wrote event for AU health state:0
2017-01-31 12:23:47:950 304 117c AU AU finished delayed initialization
2017-01-31 12:24:46:231 2516 c0c Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-31 12:24:46:231 2516 c0c Misc = Process: C:\Windows\system32\wusa.exe
2017-01-31 12:24:46:231 2516 c0c Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-31 12:24:46:231 2516 c0c COMAPI ———– COMAPI: IUpdateServiceManager::AddScanPackageService ———–
2017-01-31 12:24:46:231 2516 c0c COMAPI – ServiceName = Windows Update Standalone Installer
2017-01-31 12:24:46:231 2516 c0c COMAPI – ScanFileLocation = C:\a9f6eba08dc400ac952d\wsusscan.cab
2017-01-31 12:24:46:340 304 2e8 Misc Validating signature for C:\Windows\SoftwareDistribution\ScanFile\ed12b601-3003-4584-b24d-2d045949c1eb\Source.cab with dwProvFlags 0x00000080:
2017-01-31 12:24:46:465 304 2e8 Misc Microsoft signed: Yes
2017-01-31 12:24:46:543 304 2e8 DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2017-01-31 12:24:46:559 2516 c0c COMAPI – Added scan package service, ServiceID = {ED12B601-3003-4584-B24D-2D045949C1EB} Third party service
2017-01-31 12:24:46:559 2516 c0c COMAPI ————-
2017-01-31 12:24:46:559 2516 c0c COMAPI — START — COMAPI: Search [ClientId = wusa]
2017-01-31 12:24:46:559 2516 c0c COMAPI ———
2017-01-31 12:24:46:559 2516 c0c COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = wusa]
2017-01-31 12:25:31:124 304 9fc AU Triggering AU detection through DetectNow API
2017-01-31 12:25:31:139 304 9fc AU Triggering Online detection (interactive)
2017-01-31 12:25:31:139 304 117c AU #############
2017-01-31 12:25:31:139 304 117c AU ## START ## AU: Search for updates
2017-01-31 12:25:31:139 304 117c AU #########
2017-01-31 12:25:31:139 304 117c AU # WARNING: Failed to find updates with error code 8024001F
2017-01-31 12:25:31:139 304 117c AU #########
2017-01-31 12:25:31:139 304 117c AU ## END ## AU: Search for updates [CallId = {00000000-0000-0000-0000-000000000000}]
2017-01-31 12:25:31:139 304 117c AU #############
2017-01-31 12:25:31:139 304 117c AU Successfully wrote event for AU health state:0
2017-01-31 12:25:31:139 304 117c AU Successfully wrote event for AU health state:0
2017-01-31 12:27:01:624 304 117c AU ########### AU: Uninitializing Automatic Updates ###########
2017-01-31 12:27:01:624 304 15bc Agent * WARNING: Failed to filter search results, error = 0x8024000B
2017-01-31 12:27:01:827 304 15bc Agent *********
2017-01-31 12:27:01:827 304 15bc Agent ** END ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-31 12:27:01:827 304 15bc Agent *************
2017-01-31 12:27:01:827 2568 144c COMAPI >>– RESUMED — COMAPI: Search [ClientId = LogMeIn]
2017-01-31 12:27:01:827 2568 144c COMAPI – Updates found = 0
2017-01-31 12:27:01:827 2568 144c COMAPI – WARNING: Exit code = 0x00000000, Result code = 0x8024001E
2017-01-31 12:27:01:827 304 117c Agent WARNING: WU client fails to call back to search call {7A343F0C-C8EF-41D0-8078-E1E046E4568A} with error 0x800706ba
2017-01-31 12:27:01:827 2568 144c COMAPI ———
2017-01-31 12:27:01:827 2568 144c COMAPI — END — COMAPI: Search [ClientId = LogMeIn]
2017-01-31 12:27:01:827 2568 144c COMAPI ————-
2017-01-31 12:27:01:827 304 117c Agent Sending shutdown notification to client
2017-01-31 12:27:01:827 2568 5d4 COMAPI WARNING: Received service shutdown/self-update notification.
2017-01-31 12:27:01:827 2568 1094 COMAPI WARNING: Operation failed due to earlier error, hr=8024001E
2017-01-31 12:27:01:827 2568 1094 COMAPI FATAL: Unable to complete asynchronous search. (hr=8024001E)
2017-01-31 12:27:01:827 304 117c Agent Sending shutdown notification to client
2017-01-31 12:27:01:827 304 117c Agent Sending shutdown notification to client
2017-01-31 12:27:02:107 304 117c Service *********
2017-01-31 12:27:02:107 304 117c Service ** END ** Service: Service exit [Exit code = 0x240001]
2017-01-31 12:27:02:107 304 117c Service *************
2017-01-31 12:27:24:349 3040 5d0 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-31 12:27:24:349 3040 5d0 Misc = Process: C:\Windows\system32\wusa.exe
2017-01-31 12:27:24:349 3040 5d0 Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-31 12:27:24:349 3040 5d0 COMAPI ———– COMAPI: IUpdateServiceManager::AddScanPackageService ———–
2017-01-31 12:27:24:349 3040 5d0 COMAPI – ServiceName = Windows Update Standalone Installer
2017-01-31 12:27:24:349 3040 5d0 COMAPI – ScanFileLocation = C:\c08e1b7dedb1683077\wsusscan.cab
2017-01-31 12:27:31:868 2568 1094 COMAPI FATAL: Unable to connect to the service (hr=80080005)
2017-01-31 12:27:31:868 2568 1094 COMAPI WARNING: Unable to establish connection to the service. (hr=80080005)
2017-01-31 12:27:31:868 2568 1094 COMAPI ————-
2017-01-31 12:27:31:868 2568 1094 COMAPI — START — COMAPI: Search [ClientId = LogMeIn]
2017-01-31 12:27:31:868 2568 1094 COMAPI ———
2017-01-31 12:27:31:868 304 c64 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-31 12:27:31:868 304 c64 Misc = Process: C:\Windows\system32\svchost.exe
2017-01-31 12:27:31:868 304 c64 Misc = Module: c:\windows\system32\wuaueng.dll
2017-01-31 12:27:31:868 304 c64 Service *************
2017-01-31 12:27:31:868 304 c64 Service ** START ** Service: Service startup
2017-01-31 12:27:31:868 304 c64 Service *********
2017-01-31 12:27:31:883 304 c64 Agent * WU client version 7.6.7601.19161
2017-01-31 12:27:31:883 304 c64 Agent * Base directory: C:\Windows\SoftwareDistribution
2017-01-31 12:27:31:883 304 c64 Agent * Access type: No proxy
2017-01-31 12:27:31:883 304 c64 Agent * Network state: Disconnected
2017-01-31 12:27:31:915 304 2e8 Report CWERReporter::Init succeeded
2017-01-31 12:27:31:915 304 2e8 Agent *********** Agent: Initializing Windows Update Agent ***********
2017-01-31 12:27:31:915 304 ae8 Agent *********** Agent: Initializing Windows Update Agent ***********
2017-01-31 12:27:31:930 304 2e8 Agent * Prerequisite roots succeeded.
2017-01-31 12:27:31:930 304 2e8 Agent *********** Agent: Initializing global settings cache ***********
2017-01-31 12:27:31:930 304 2e8 Agent * WSUS server: <NULL>
2017-01-31 12:27:31:930 304 2e8 Agent * WSUS status server: <NULL>
2017-01-31 12:27:31:930 304 2e8 Agent * Target group: (Unassigned Computers)
2017-01-31 12:27:31:930 304 2e8 Agent * Windows Update access disabled: No
2017-01-31 12:27:31:930 304 2e8 Agent * Found 1 persisted download calls to restore
2017-01-31 12:27:31:930 304 2e8 Agent WARNING: WU client failed to initialize a download call from persisted data with potential error 0x80248002
2017-01-31 12:27:31:930 304 2e8 DnldMgr Download manager restoring 0 downloads
2017-01-31 12:27:31:930 304 2e8 Agent * Failed to load persisted download calls, error = 0x80248002
2017-01-31 12:27:32:367 304 c64 Report *********** Report: Initializing static reporting data ***********
2017-01-31 12:27:32:367 304 c64 Report * OS Version = 6.1.7601.1.0.65792
2017-01-31 12:27:32:367 304 c64 Report * OS Product Type = 0x00000004
2017-01-31 12:27:32:383 304 c64 Report * Computer Brand = Hewlett-Packard
2017-01-31 12:27:32:383 304 c64 Report * Computer Model = HP xw4400 Workstation
2017-01-31 12:27:32:383 304 c64 Report * Bios Revision = 786D7 v02.03
2017-01-31 12:27:32:383 304 c64 Report * Bios Name = Default System BIOS
2017-01-31 12:27:32:383 304 c64 Report * Bios Release Date = 2006-04-04T00:00:00
2017-01-31 12:27:32:383 304 c64 Report * Locale ID = 1033
2017-01-31 12:27:32:476 2568 1094 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = LogMeIn]
2017-01-31 12:27:32:492 304 ae8 Misc Validating signature for C:\Windows\SoftwareDistribution\ScanFile\5f3d076f-299e-45c8-a28d-2d82004440a2\Source.cab with dwProvFlags 0x00000080:
2017-01-31 12:27:32:492 304 ae8 Misc Microsoft signed: Yes
2017-01-31 12:27:32:523 304 ae8 DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2017-01-31 12:27:32:523 3040 5d0 COMAPI – Added scan package service, ServiceID = {5F3D076F-299E-45C8-A28D-2D82004440A2} Third party service
2017-01-31 12:27:32:523 3040 5d0 COMAPI ————-
2017-01-31 12:27:32:523 3040 5d0 COMAPI — START — COMAPI: Search [ClientId = wusa]
2017-01-31 12:27:32:523 3040 5d0 COMAPI ———
2017-01-31 12:27:32:523 3040 5d0 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = wusa]
2017-01-31 12:27:32:539 304 26c Agent *************
2017-01-31 12:27:32:539 304 26c Agent ** START ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-31 12:27:32:539 304 26c Agent *********
2017-01-31 12:27:32:539 304 26c Agent * Online = No; Ignore download priority = No
2017-01-31 12:27:32:539 304 26c Agent * Criteria = “IsInstalled = 0 AND IsHidden = 0”
2017-01-31 12:27:32:539 304 26c Agent * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2017-01-31 12:27:32:539 304 26c Agent * Search Scope = {Machine}
2017-01-31 12:27:34:005 304 26c Driver Matched driver to device USB\VID_046D&PID_081A&REV_0010&MI_02
2017-01-31 12:27:34:005 304 26c Driver Status: 0x180200a, ProblemNumber: 00000000
2017-01-31 12:28:16:921 304 c64 AU ########### AU: Initializing Automatic Updates ###########
2017-01-31 12:28:16:921 304 c64 AU # AU disabled through User preference
2017-01-31 12:28:16:921 304 c64 AU Initializing featured updates
2017-01-31 12:28:16:921 304 c64 AU Found 0 cached featured updates
2017-01-31 12:28:16:921 304 c64 AU Successfully wrote event for AU health state:0
2017-01-31 12:28:16:921 304 c64 AU Successfully wrote event for AU health state:0
2017-01-31 12:28:16:921 304 c64 AU AU finished delayed initialization
2017-01-31 15:17:17:633 304 c64 AU Sending shutdown notification
2017-01-31 15:17:17:633 304 c64 AU AU initiates service shutdown
2017-01-31 15:17:17:633 304 c64 AU ########### AU: Uninitializing Automatic Updates ###########
2017-01-31 15:17:17:633 304 26c Agent * WARNING: Failed to filter search results, error = 0x8024000B
2017-01-31 15:17:18:164 304 26c Agent *********
2017-01-31 15:17:18:164 304 26c Agent ** END ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-31 15:17:18:164 304 26c Agent *************
2017-01-31 15:17:18:179 2568 1170 COMAPI >>– RESUMED — COMAPI: Search [ClientId = LogMeIn]
2017-01-31 15:17:18:179 2568 1170 COMAPI – Updates found = 0
2017-01-31 15:17:18:179 2568 1170 COMAPI – WARNING: Exit code = 0x00000000, Result code = 0x8024001E
2017-01-31 15:17:18:179 2568 1170 COMAPI ———
2017-01-31 15:17:18:179 2568 1170 COMAPI — END — COMAPI: Search [ClientId = LogMeIn]
2017-01-31 15:17:18:179 304 c64 Agent WARNING: WU client fails to call back to search call {8FAF1DB4-A06E-4A91-AD3B-912E537DA93B} with error 0x800706ba
2017-01-31 15:17:18:179 2568 1170 COMAPI ————-
2017-01-31 15:17:18:179 304 c64 Agent Sending shutdown notification to client
2017-01-31 15:17:18:179 2568 1094 COMAPI WARNING: Operation failed due to earlier error, hr=8024001E
2017-01-31 15:17:18:179 2568 1094 COMAPI FATAL: Unable to complete asynchronous search. (hr=8024001E)
2017-01-31 15:17:18:179 2568 1538 COMAPI WARNING: Received service shutdown/self-update notification.
2017-01-31 15:17:18:179 304 c64 Agent Sending shutdown notification to client
2017-01-31 15:17:18:179 304 c64 Agent Sending shutdown notification to client
2017-01-31 15:17:18:507 304 c64 Service *********
2017-01-31 15:17:18:507 304 c64 Service ** END ** Service: Service exit [Exit code = 0x240001]
2017-01-31 15:17:18:507 304 c64 Service *************
2017-01-31 15:19:14:071 392 a8c Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-31 15:19:14:071 392 a8c Misc = Process: C:\Windows\system32\svchost.exe
2017-01-31 15:19:14:071 392 a8c Misc = Module: c:\windows\system32\wuaueng.dll
2017-01-31 15:19:14:071 392 a8c Service *************
2017-01-31 15:19:14:071 392 a8c Service ** START ** Service: Service startup
2017-01-31 15:19:14:071 392 a8c Service *********
2017-01-31 15:19:14:180 392 a8c Agent * WU client version 7.6.7601.19161
2017-01-31 15:19:14:180 392 a8c Agent * Base directory: C:\Windows\SoftwareDistribution
2017-01-31 15:19:14:180 392 a8c Agent * Access type: No proxy
2017-01-31 15:19:14:196 392 a8c Agent * Network state: Connected
2017-01-31 15:19:14:570 392 4b4 Report CWERReporter::Init succeeded
2017-01-31 15:19:14:570 392 4b4 Agent *********** Agent: Initializing Windows Update Agent ***********
2017-01-31 15:19:14:570 392 4b4 Agent * Prerequisite roots succeeded.
2017-01-31 15:19:14:570 392 4b4 Agent *********** Agent: Initializing global settings cache ***********
2017-01-31 15:19:14:570 392 4b4 Agent * WSUS server: <NULL>
2017-01-31 15:19:14:570 392 4b4 Agent * WSUS status server: <NULL>
2017-01-31 15:19:14:570 392 4b4 Agent * Target group: (Unassigned Computers)
2017-01-31 15:19:14:570 392 4b4 Agent * Windows Update access disabled: No
2017-01-31 15:19:14:570 392 4b4 Agent * Found 1 persisted download calls to restore
2017-01-31 15:19:14:570 392 4b4 Agent WARNING: WU client failed to initialize a download call from persisted data with potential error 0x80248002
2017-01-31 15:19:14:570 392 4b4 DnldMgr Download manager restoring 0 downloads
2017-01-31 15:19:14:570 392 4b4 Agent * Failed to load persisted download calls, error = 0x80248002
2017-01-31 15:19:16:083 2424 b04 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-31 15:19:16:083 2424 b04 Misc = Process: C:\Program Files (x86)\LogMeIn\x64\LogMeIn.exe
2017-01-31 15:19:16:083 2424 b04 Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-31 15:19:16:083 2424 b04 COMAPI ————-
2017-01-31 15:19:16:083 2424 b04 COMAPI — START — COMAPI: Search [ClientId = LogMeIn]
2017-01-31 15:19:16:083 2424 b04 COMAPI ———
2017-01-31 15:19:16:083 2424 b04 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = LogMeIn]
2017-01-31 15:19:16:146 392 a8c Report *********** Report: Initializing static reporting data ***********
2017-01-31 15:19:16:146 392 a8c Report * OS Version = 6.1.7601.1.0.65792
2017-01-31 15:19:16:146 392 a8c Report * OS Product Type = 0x00000004
2017-01-31 15:19:16:177 392 a8c Report * Computer Brand = Hewlett-Packard
2017-01-31 15:19:16:177 392 a8c Report * Computer Model = HP xw4400 Workstation
2017-01-31 15:19:16:192 392 a8c Report * Bios Revision = 786D7 v02.03
2017-01-31 15:19:16:192 392 a8c Report * Bios Name = Default System BIOS
2017-01-31 15:19:16:192 392 a8c Report * Bios Release Date = 2006-04-04T00:00:00
2017-01-31 15:19:16:192 392 a8c Report * Locale ID = 1033
2017-01-31 15:19:19:141 392 c44 Agent *************
2017-01-31 15:19:19:141 392 c44 Agent ** START ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-31 15:19:19:141 392 c44 Agent *********
2017-01-31 15:19:19:141 392 c44 Agent * Online = No; Ignore download priority = No
2017-01-31 15:19:19:141 392 c44 Agent * Criteria = “IsInstalled = 0 AND IsHidden = 0”
2017-01-31 15:19:19:141 392 c44 Agent * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2017-01-31 15:19:19:141 392 c44 Agent * Search Scope = {Machine}
2017-01-31 15:19:19:640 392 c44 Driver Matched driver to device USB\VID_046D&PID_081A&REV_0010&MI_02
2017-01-31 15:19:19:640 392 c44 Driver Status: 0x180200a, ProblemNumber: 00000000
2017-01-31 15:19:59:451 392 a8c AU ########### AU: Initializing Automatic Updates ###########
2017-01-31 15:19:59:467 392 a8c AU # AU disabled through User preference
2017-01-31 15:19:59:467 392 a8c AU Initializing featured updates
2017-01-31 15:19:59:467 392 a8c AU Found 0 cached featured updates
2017-01-31 15:19:59:482 392 a8c AU Successfully wrote event for AU health state:0
2017-01-31 15:19:59:482 392 a8c AU Successfully wrote event for AU health state:0
2017-01-31 15:19:59:482 392 a8c AU AU finished delayed initialization
2017-01-31 15:29:30:843 4828 ebc Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-31 15:29:30:843 4828 ebc Misc = Process: c:\Program Files\Microsoft Security Client\MpCmdRun.exe
2017-01-31 15:29:30:843 4828 ebc Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-31 15:29:30:842 4828 ebc COMAPI ————-
2017-01-31 15:29:30:843 4828 ebc COMAPI — START — COMAPI: Search [ClientId = Microsoft Security Essentials (EDB4FA23-53B8-4AFA-8C5D-99752CCA7094)]
2017-01-31 15:29:30:843 4828 ebc COMAPI ———
2017-01-31 15:29:30:851 4828 ebc COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = Microsoft Security Essentials (EDB4FA23-53B8-4AFA-8C5D-99752CCA7094)]
2017-01-31 16:39:46:102 392 a8c AU ########### AU: Uninitializing Automatic Updates ###########
2017-01-31 16:39:46:102 392 c44 Agent * WARNING: Failed to filter search results, error = 0x8024000B
2017-01-31 16:39:46:835 392 c44 Agent *********
2017-01-31 16:39:46:835 392 c44 Agent ** END ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-31 16:39:46:835 392 c44 Agent *************
2017-01-31 16:39:46:861 2424 1338 COMAPI >>– RESUMED — COMAPI: Search [ClientId = LogMeIn]
2017-01-31 16:39:46:862 2424 1338 COMAPI – Updates found = 0
2017-01-31 16:39:46:862 2424 1338 COMAPI – WARNING: Exit code = 0x00000000, Result code = 0x8024001E
2017-01-31 16:39:46:862 2424 1338 COMAPI ———
2017-01-31 16:39:46:862 2424 1338 COMAPI — END — COMAPI: Search [ClientId = LogMeIn]
2017-01-31 16:39:46:862 2424 1338 COMAPI ————-
2017-01-31 16:39:46:875 4828 e7c COMAPI >>– RESUMED — COMAPI: Search [ClientId = Microsoft Security Essentials (EDB4FA23-53B8-4AFA-8C5D-99752CCA7094)]
2017-01-31 16:39:46:877 4828 e7c COMAPI – Updates found = 0
2017-01-31 16:39:46:877 4828 e7c COMAPI – WARNING: Exit code = 0x00000000, Result code = 0x8024001E
2017-01-31 16:39:46:877 4828 e7c COMAPI ———
2017-01-31 16:39:46:877 4828 e7c COMAPI — END — COMAPI: Search [ClientId = Microsoft Security Essentials (EDB4FA23-53B8-4AFA-8C5D-99752CCA7094)]
2017-01-31 16:39:46:877 4828 e7c COMAPI ————-
2017-01-31 16:39:46:877 4828 124c COMAPI WARNING: Operation failed due to earlier error, hr=8024001E
2017-01-31 16:39:46:877 4828 124c COMAPI FATAL: Unable to complete asynchronous search. (hr=8024001E)
2017-01-31 16:39:46:891 2424 b04 COMAPI WARNING: Operation failed due to earlier error, hr=8024001E
2017-01-31 16:39:46:891 2424 b04 COMAPI FATAL: Unable to complete asynchronous search. (hr=8024001E)
2017-01-31 16:39:46:876 392 a8c Agent Sending shutdown notification to client
2017-01-31 16:39:46:909 2424 4f0 COMAPI WARNING: Received service shutdown/self-update notification.
2017-01-31 16:39:46:910 392 a8c Agent Sending shutdown notification to client
2017-01-31 16:39:46:910 4828 e7c COMAPI WARNING: Received service shutdown/self-update notification.
2017-01-31 16:39:47:569 392 a8c Service *********
2017-01-31 16:39:47:569 392 a8c Service ** END ** Service: Service exit [Exit code = 0x240001]
2017-01-31 16:39:47:575 392 a8c Service *************
2017-01-31 16:40:16:976 2424 b04 COMAPI FATAL: Unable to connect to the service (hr=80080005)
2017-01-31 16:40:16:976 2424 b04 COMAPI WARNING: Unable to establish connection to the service. (hr=80080005)
2017-01-31 16:40:17:140 392 1390 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-31 16:40:17:140 392 1390 Misc = Process: C:\Windows\system32\svchost.exe
2017-01-31 16:40:17:140 392 1390 Misc = Module: c:\windows\system32\wuaueng.dll
2017-01-31 16:40:17:140 392 1390 Service *************
2017-01-31 16:40:17:140 392 1390 Service ** START ** Service: Service startup
2017-01-31 16:40:17:140 392 1390 Service *********
2017-01-31 16:40:17:210 392 1390 Agent * WU client version 7.6.7601.19161
2017-01-31 16:40:17:223 392 1390 Agent * Base directory: C:\Windows\SoftwareDistribution
2017-01-31 16:40:17:223 392 1390 Agent * Access type: No proxy
2017-01-31 16:40:17:242 392 1390 Agent * Network state: Connected
2017-01-31 16:40:17:579 392 10e4 Report CWERReporter::Init succeeded
2017-01-31 16:40:17:579 392 10e4 Agent *********** Agent: Initializing Windows Update Agent ***********
2017-01-31 16:40:17:633 392 10e4 Agent * Prerequisite roots succeeded.
2017-01-31 16:40:17:634 392 10e4 Agent *********** Agent: Initializing global settings cache ***********
2017-01-31 16:40:17:634 392 10e4 Agent * WSUS server: <NULL>
2017-01-31 16:40:17:634 392 10e4 Agent * WSUS status server: <NULL>
2017-01-31 16:40:17:634 392 10e4 Agent * Target group: (Unassigned Computers)
2017-01-31 16:40:17:634 392 10e4 Agent * Windows Update access disabled: No
2017-01-31 16:40:17:666 392 10e4 Agent * Found 1 persisted download calls to restore
2017-01-31 16:40:17:667 392 10e4 Agent WARNING: WU client failed to initialize a download call from persisted data with potential error 0x80248002
2017-01-31 16:40:17:667 392 10e4 DnldMgr Download manager restoring 0 downloads
2017-01-31 16:40:17:667 392 10e4 Agent * Failed to load persisted download calls, error = 0x80248002
2017-01-31 16:40:17:687 2424 b04 COMAPI ————-
2017-01-31 16:40:17:687 2424 b04 COMAPI — START — COMAPI: Search [ClientId = LogMeIn]
2017-01-31 16:40:17:687 2424 b04 COMAPI ———
2017-01-31 16:40:17:735 2424 b04 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = LogMeIn]
2017-01-31 16:40:20:407 392 1390 Report *********** Report: Initializing static reporting data ***********
2017-01-31 16:40:20:407 392 1390 Report * OS Version = 6.1.7601.1.0.65792
2017-01-31 16:40:20:407 392 1390 Report * OS Product Type = 0x00000004
2017-01-31 16:40:20:519 392 1390 Report * Computer Brand = Hewlett-Packard
2017-01-31 16:40:20:519 392 1390 Report * Computer Model = HP xw4400 Workstation
2017-01-31 16:40:20:523 392 1390 Report * Bios Revision = 786D7 v02.03
2017-01-31 16:40:20:523 392 1390 Report * Bios Name = Default System BIOS
2017-01-31 16:40:20:523 392 1390 Report * Bios Release Date = 2006-04-04T00:00:00
2017-01-31 16:40:20:523 392 1390 Report * Locale ID = 1033
2017-01-31 16:40:23:384 392 14fc Agent *************
2017-01-31 16:40:23:385 392 14fc Agent ** START ** Agent: Finding updates [CallerId = LogMeIn]
2017-01-31 16:40:23:385 392 14fc Agent *********
2017-01-31 16:40:23:385 392 14fc Agent * Online = No; Ignore download priority = No
2017-01-31 16:40:23:385 392 14fc Agent * Criteria = “IsInstalled = 0 AND IsHidden = 0”
2017-01-31 16:40:23:385 392 14fc Agent * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2017-01-31 16:40:23:385 392 14fc Agent * Search Scope = {Machine}
2017-01-31 16:40:25:682 392 14fc Driver Matched driver to device USB\VID_046D&PID_081A&REV_0010&MI_02
2017-01-31 16:40:25:683 392 14fc Driver Status: 0x180200a, ProblemNumber: 00000000
2017-01-31 16:41:02:520 392 1390 AU ########### AU: Initializing Automatic Updates ###########
2017-01-31 16:41:02:521 392 1390 AU # AU disabled through User preference
2017-01-31 16:41:02:521 392 1390 AU Initializing featured updates
2017-01-31 16:41:02:521 392 1390 AU Found 0 cached featured updates
2017-01-31 16:41:02:521 392 1390 AU Successfully wrote event for AU health state:0
2017-01-31 16:41:02:522 392 1390 AU Successfully wrote event for AU health state:0
2017-01-31 16:41:02:522 392 1390 AU AU finished delayed initialization
2017-01-31 16:41:37:113 4768 1480 Misc =========== Logging initialized (build: 7.6.7601.19161, tz: -0500) ===========
2017-01-31 16:41:37:113 4768 1480 Misc = Process: C:\Windows\system32\wusa.exe
2017-01-31 16:41:37:113 4768 1480 Misc = Module: C:\Windows\system32\wuapi.dll
2017-01-31 16:41:36:513 4768 1480 COMAPI ———– COMAPI: IUpdateServiceManager::AddScanPackageService ———–
2017-01-31 16:41:37:113 4768 1480 COMAPI – ServiceName = Windows Update Standalone Installer
2017-01-31 16:41:37:114 4768 1480 COMAPI – ScanFileLocation = C:\1ee7616080bb0ff10074e5d1ac99fe\wsusscan.cab
2017-01-31 16:41:37:137 392 109c Misc Validating signature for C:\Windows\SoftwareDistribution\ScanFile\407f3057-dc24-4078-89e9-bf367023e2d3\Source.cab with dwProvFlags 0x00000080:
2017-01-31 16:41:38:195 392 109c Misc Microsoft signed: Yes
2017-01-31 16:41:38:868 392 109c DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2017-01-31 16:41:38:904 4768 1480 COMAPI – Added scan package service, ServiceID = {407F3057-DC24-4078-89E9-BF367023E2D3} Third party service
2017-01-31 16:41:38:905 4768 1480 COMAPI ————-
2017-01-31 16:41:38:905 4768 1480 COMAPI — START — COMAPI: Search [ClientId = wusa]
2017-01-31 16:41:38:905 4768 1480 COMAPI ———
2017-01-31 16:41:38:910 4768 1480 COMAPI <<– SUBMITTED — COMAPI: Search [ClientId = wusa]

Reply | Quote

Do the following…

Open an elevated Command prompt (Run as Administrator)…

1. Type: “net stop wuauserv” (no quotes for everything) and press enter.

2. Type: “ren softwaredistribution softwaredistribution.old” and press enter.

3. Type: “net start wuauserv” and press enter.

Close the Command prompt window and try updating again.

Note: If you are trying to update logged in as a Standard user, and all users don’t have permissions to update, then you will need to be logged in as an Administrator.

Thanks again.
It couldn’t seem to find the file softwaredistribution.
I don’t know if I copied this exactly, but here’s what I got:

Microsoft Windows [Uersion 6.1.7601]
Copyright <c> 2009 Microsoft Corporation. All rights reserved.
C:\Windows\systen32>net stop wuasuerv
The service name is invalid.
More help is available by typing NET HELPMSC 2185.
C:\Windows\system32>net stop wuauserv
The Windows Update service is stopping.
The Windows Update service was stopped successfully.
C:\Windows\system32>ren softwaredistribution softwaredistribution.old [he systen cannot find the file specified.
C:\Windows\system32>ren softwaredistribution softwaredistribution.old [he systen cannot find the file specified.
C:\Windows\system32>net start wuauserv
The requested service has already been started.
More help is available by typing NET HELPMSC 2182.
C: \Windows\system32>

Reply | Quote

“I don’t know if I copied this exactly, but here’s what I got:”

You actually don’t need to hand copy text that is displayed in the Command prompt window.

You can do the following…

1. Place your cursor in the upper left hand corner of the window, right where the little icon is.

2. Right click, click Edit, then click Select All. The background and fonts will reverse color.

3. Then, just hit Enter.

You can then paste the contents into Notepad.

Ha! Shows how much I know. I got as far as the reverse color, then tried Ctrl-C. After that didn’t work, I made a screenshot and saved an OCR of it. Only it changed a lot of the letters (m to n and W to l[)!
A little ignorance goes a long way.
Thanks again.

Reply | Quote

@morty

Sorry, my fault. I left out an important step.

Here are the revised steps…

Open an elevated Command prompt (Run as Administrator)…

1. Type: “cd %windir%” (no quotes for everything) and press enter.

2. Type: “net stop wuauserv” and press enter.

3. Type: “ren softwaredistribution softwaredistribution.old” and press enter.

4. Type: “net start wuauserv” and press enter.

Close the Command prompt window and try updating again.

Note: If you are trying to update logged in as a Standard user, and all users don’t have permissions to update, then you will need to be logged in as an Administrator.

Thanks again.
Do I still have to disconnect the internet before I run the installer?
If yes, is there a neater way to do it than pulling the ethernet plug from my router? (I once clicked on Disconnect in the “Network and Sharing Center” and it was a whole song and dance to reconnect it!)
Morty

Reply | Quote

Those who require internet disconnected, or configuration set to Never check for updates are generally those who have patching problems or are not patched up to date.
The internet connection tries to “repair” the DataStore.edb based on most recent information available at Microsoft (I can’t find the reference now). But if the DataStore.edb is already corrupted beyond basic repair and not reset before manual updating, then the database repair fails and the installation times out or in more fortunate instances, it takes a long time to complete.
This is why it is often recommended to disconnect from the internet or disable the NIC or something equivalent.

Reply | Quote

I don’t see much point in defragging the DataStore.edb offline vs rebuilding.
It may avoid downloading a large amount of data though.

Reply | Quote