Replies

@JohnFDoe: Your assumption may be right – but they left a “backdoor” within the system, that may have been used easily to send keystrokes remotely.

 

Anyway, HP released another conexant audio driver with a ‘deactivated’ keylogger …

… then they released days later just another conexant audio driver, finally with a removed keylogger.

But not to mention any change log (as far as I’ve seen – I’m not a native English language speaker – on their Security Advisory site with driver update links – seems not too smart (even not informing the ‘finder’ of the keylogger, Mr. Schröder, about their plans).

BTW: I’ve documented the latest steps within the blog post The HP Conexant audio driver ‘stop key logger’ placebo update.

 

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

1 user thanked author for this post.

woody

Either the update is distributed accidentially – or they changed something and avoided to update their manifest description for Windows Update and Microsoft Update Catalog and for KB-article KB3008923. My conclusion: The update thing at MS is terrible broken – some observations and thoughs may be found at Internet Explorer 11 Update KB3008923 (May 2017) is back within my blog.

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

1 user thanked author for this post.

woody

Hm, was able to download Update kb3128031 from their site and from Microsoft Update Catalog 05/04/2017 10:00PM CET.

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

KB3217877 hasn’t documented till yet. As far as I has seen, they are patching several things link Universal C runtime (UCRT). I guess, it’s some issue fixes.

Update KB4012864 has been covered here: Windows 7/8.1/Server: WSUS-Update KB4012864

Ok, I wrote a blog post KB3217877 summing up the things here:
Update KB3217877 for Windows Vista/Server 2008

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

1 user thanked author for this post.

Pim

I received a user comment, that Update KB4013429 breaks again Windows System Restore

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

1 user thanked author for this post.

woody

Now Microsoft has published a statement at MS Answers about that issue. I wrote a blog post with additional information at Microsoft’s Fix for the ‘Microsoft – WPD – 2/22/2016 12:00:00 AM – 5.2.5326.4762’ driver issue

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

5 users thanked author for this post.

rc primak, satrow, walker, woody, ch100

This update is available for Windows 7, 8.1 and 10. The package contains USB driver für MediaTek Android devices and also some MTP WPD driver. It seems that those drivers are conflicting with already installed ADB-, USB- and MTP drivers.

I got reports from several users, that mobile devices are nor more recognized after this update has been installed (usb and bluetooth). It affects Android devices as well as Lumias.

I will have published a blog post an March 9, 2017 about that at Windows update: Microsoft – WPD – 2/22/2016 12:00:00 AM – 5.2.5326.4762

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

7 users thanked author for this post.

Elly, SueW, ch100, woody, dononline, PhotM, lizzytish

Noel Carboni wrote:

woody wrote:

There’s a fix, but it ain’t pretty.

??? All I see in that article are 4 of what honestly look more like shots in the dark than “fixes” to me. Item 2 has some merit. For folks having System Restore failures: Have you tried doing the System Restore from a bootup WinRE (recovery environment)? That way works for me a lot better than trying to initiate it on a running system. See below for some guidance as to how to get into it… -Noel     

Well, your right – at the time I wrote the first version of this article, I’ve had no clue, that I would get in touch with this error. So Fixes #1 – #4 was a “shot in the dark” . Then I developed #fix 5 and provided all fixes to users asked for help in German Microsoft Answers forum.

They came back, that Windows PE system restore didn’t help. And they came back, that renaming folder WindowsApps brought system restore back to operation. Later on, I became involved in the discussion held at US MS answers forum (linked within my blog post), where the command prompt command sequence was refined.

Within my German blog post I received first hints, that it could have something to do with January 2017 update.

And if you ever tried to nail down a system restore error, perhaps you are aware, that it may take 1-2 hours for a test run. So the final fix and the explanation, that KB 3213986 is involved is the result of many hours of testing from several users (including me).

That’s in short the whole story (but I have also to confess, that my two articles, one in German and one in English are getting slight different in time, due to the fact, that the whole case was a kind of ‘moving target’ over the time) …

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

From what I found out (also from comments received from German readers), two apps – EarTrumpet and Office Hub – seems to be involved, It seems that the sub folder VFS (for virtual file system content) contains NTFS links that could not be written back. We suppose, that this could be the reason for the issue.

One reader informed me today, that EarTrumpet app has been updated, so the VFS folder has been gone.

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

But there is another crude thing – it seems that WSUS is broken. I’ve published some details here: Windows 10 Update KB4013868: Is Microsoft’s WSUS broken?

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

The things found so far has been documented at Windows 10 Update KB3213986 kills system restore. I guess, Woody will sum it up later.

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

Think we have to wait. My sources told me, that MS is planning to ship a Flash update before March 14, 2017 – but no shipping date confirmed yet.

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

4 users thanked author for this post.

walker, Elly, Woody Lounger, PKCano

Concering the “Something Happened 0x80070005-0x90002” error:

0x80070005 stands for ERROR_ACCESS_DENIED

The extended error code 0x90002 should specify the phase, where the error occurs. Unfortunately 9 isn’t documented, 02 is probably SP_EXECUTION_OP_COPY_PAYLOAD. Details may be obtained from log files.

See:
http://borncity.com/win/2016/10/15/windows-10-analyze-upgrade-errors/
http://borncity.com/win/2016/07/05/how-to-decode-windows-errors/
https://technet.microsoft.com/en-us/itpro/windows/deploy/resolve-windows-10-upgrade-errors?f=255&MSPPError=-2147217396

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

2 users thanked author for this post.

woody, PKCano

From what I have found out, in many cases wrong disc drivers are the reason, why a cloned os won’t boot. For my own, I have tested it intensive with VMware Player and VirtualBox. In both cases, the cloned Win XP came with a IDE driver, whilst the VM provides SCSI oder SATA disks. I solved it using VMware Converter to create a .vmdk, that was bootable at least (but the clone is pretty slow).

So as a conclusion, I gave up cloning and use instead a clean install (either on a .vhd or .vdi or .vmdk disk).

I have written a bit about this issues in my blog (http://www.borncity.com/blog/category/virtualisierung/) – but the whole stuff is only in German – sorry.

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

One option to replace Steady State is VHD boot (unfortunately only available for Win 7 Ultimate). But then you can use differential disks, that will be resetteable.

Also virtualisation will be an option to solve this issue – but this isn’t free of charge.

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/