niko32

Haha, I often come here to read @glnz posts, just for that extra comical effect. I remember that I transferred my OE emails to Thunderbird, but it was a decade or more ago, I don't even remember how I did it, so sorry I can't help with that. As for the XP after the last patch Tuesday, I intend to use it as long as it is possible, not just because I like it, but for my current hardware is not capable for running something newer, except some Linux distros, which I use from time to time. And I have no doubt, this great XP loving community at MSFN, and some others will still be alive and kicking, for years to come.

@w2k4eva You've made a really thorough investigation about it. It made me remember that is the way I got it, from WINUSB_UPDATE_XP-SRV03.exe. Now, after downloading and extracting files from that update package and comparing it to my files winusb.dll and winusb.sys, they are identical and of same version 6.1.7600.16385, called Windows USB Class Driver BETA. So where can I get newer winusb.sys 6.1.7600.16421 for the sake of "updateness" , I mean @Dibya's custom installer for it?

Yeah, that could be it , I've had some Samsung phone related software installed years ago. Anyway, I circumvented the problem by copying already present in system32 winusb.dll and accompanying winusb.sys in system32/drivers to some folder, and then reinstalled them from there with Add Remove Windows Components, so it doesn't complain anymore.

Thanks for replying and clarification. Mine winusb.dll is version 6.1.7600.16385 (win7_rtm.090713-1255), obviously as you noticed, came from win7 package and it is created on 02 November 2006 and modified on 07 July 2009. I thought too it was from dencorso's thread about usb updates, but apparently must have installed it from somewhere else, and data about it are pretty scarce. Anyway it isn't a big deal, but a little strange.

I'm having a strange problem, probably related to some update I don't even remember. While removing something in Control Panel - Add or Remove Programs - Add/Remove Windows Components, there's this Microsoft WinUsb 2.0 item there, that was already checked before, but now it suddenly asks for installation cd for winusb.dll file, which I already have inside system32 folder, and it's version 6.1.7600.16385. Another thing, in Control Panel - Add or Remove Programs there is installed Microsoft WinUsb 1.0. Does anyone else have this installed, and what does it do?

It's been quoted a lot, but I gotta once more, just to thank dencorso for reminding us. I used to watch for updates to TCPIP.SYS, but now I often miss it, busy times.

Thanks for input @Dave-H, so it's not just me. I unfollowed it, and than followed it again, and mail of your post arrived. Now it could be it, or not, only time will tell.

Anyone else having problem with following this thread? Few days ago, I suddenly stopped getting mails of posts from this thread. They are not blocked, or gone to spam. It didn't happened immediately after server's crash and recovery, but few days after it. Strangely, I'm still getting mails from forked Root Certificates thread.

SD73 and glnz, I didn't have to force install with that switch and both files are new 5.1.2600.7392 versions. I guess it's all about hardware and software diversity, some components get along with it better than the others. So far I haven't had any problems. glnz, with the help of knowledgeable people here, I hope You'll solve yours.

I have installed all available January patches, 2 security and 3 .NET updates, all went fine and is updated to proper version numbers. CPU is Intel Core 2 Duo T5800 (Merom) 2.00GHz, so for now I believe in Intel that this one is not affected with that potential Meltdown+Spectre attack. But where is January Cumulative Security Update for Internet Explorer 8 for WES09 and POSReady 2009, did I miss it somehow? Also, thanks Dencorso for digging out that old hal.dll KB951126 update.

So basically we using FSB Core 2 Duo processors are safe from Spectre & Meltdown security hole and don't even need possible future patch. Thanks Destro for clarifying that.

Nice find @Bersaglio. I was just preparing to download it. And after reading this post, quick registry search showed that I already got it, thanks to informations on this page, probably.

Yes, that might be it. I'm obviously not so good with tables. Thanks, dencorso!

Hm, maybe I haven't sleep enough last night, but I just can't figure out from that post what exactly are those 3 hotfixes. There are so many numbers... @glnz Well, I have noscript, adblock plus and better privacy of those firefox addons, and haven't experienced any of problems with this site You've mentioned. It might be one of other addons or something else.

That's what happens when you don't read enough, thinking you already know everything. I've completely forgot that "WindowsEmbedded" registry key was not at the same place as WEP and WEPOS registry keys. Everything's fine now, POSReady updates showed up almost instantly. Thanks bphlpt, and heinoganda

I've had no time to check it earlier, and sorry I was a little vague. Last updates to that windows XP sp3 are from February 2016: KB3134814 for IE8 and KB3126593 as in pcalvert's case. And system is not able to receive any later POSReady update. Windows Update and Microsoft Update for some reason obviously consider it as XP sp3 instead POSReady, despite the POSReady registry entry. I have installed both updates you have suggested (KB4025252 and KB942288-v3) to no avail. Now I really have no idea what to try next.

Similar problem here with my aunt's laptop. Around February 2016, I've applied POSReady hack to that computer and installed all security updates that were available for POSReady. Now that I'm servicing her laptop, problem has appeared. Now, first thing I've done is removing WEP and WEPOS registry entries as I successfully did long ago with my laptop. I removed those registry entries, but here that didn't work at all, still no POSReady updates. I have tried to remove SoftwareDistribution folder and get it back, nothing works, Windows update, Microsoft Update all the same, just optional Windows XP updates are are offered, same as with pcalvert. Any ideas, guys? Thanks

@glnz Eh good old Spider, haven't seen that program in ages. I just stumbled on that forum post, searching why I don't get MSInfo update, until I remembered that I removed it before installation. @dencorso XP is my only OS on this old laptop, but I often don't wait more than a day or two until You guys try updates out, then I jump in too. So far, much less problems with POSReady updates than there was with XP updates before it. I used to dual boot XP with Arch Linux before, but my old Hard Disk suddenly died and I haven't found enough time and will to go through painstakingly setup of Arch the way I want it.

Maybe this could be cause of your minor problem with MSInfo: http://discussions.virtualdr.com/showthread.php?111211-msinfo&p=547276#post547276 Author of the post found a solution in his/her case. I can't check it, because I don't even have MSInfo anymore. But I doubt security update would address things like that. Me too always wait a little to see is everything alright with the updates. I let the brave ones install it first, or those who don't use WinXP as their main OS.

Thanks for the info, I had no time then to look it up. Many years ago I've used nLite to customize and remove many to me unnecessary and some security risk components from xp sp3 cd. Apparently, MSInfo was one of those components. So besides I don't need it, I lack some files and services to even run it.

At my place it took half an hour, which is not that bad for my 9 years old core 2 duo laptop. I've got all updates except kb4025398, strange. Now I'm not sure should I install it manually or i don't need it at all?

Finally, they made it available for our good old systems. I had to undo some custom changes I've did to mitigate this vulnerability. Anyway, at my place standard problems with this batch of updates, high CPU usage, and .NET Framework 4 update long installation, but eventually it all came through. EDIT: It's a funny way they put it: "to protect against potential nation-state activity". (NSA)

I agree with your conclusion. But, what I wrote before is that there is apparently another, more precise way to deal with EsteemAudit exploit. Anyway it's good that even if Microsoft doesn't care, users around world can find solutions to various vulnerabilities.

Hm, heinoganda and other members of the crew, what do you think about mitigation of EsteemAudit vulnerability proposed in comment section of page: https://researchcenter.paloaltonetworks.com/2017/05/unit42-dissection-esteemaudit-windows-remote-desktop-exploit/ by commenter Jean-Claude Dusse: Interesting solution, and he too claims that Windows XP computers that are not part of a domain are practically not exposed to the exploit.

Well I'm not nearly that knowledgeable as the team leaders here. But short answer to question 2 is that KB982316 just adds extra protection for not that likely threat. Mathwiz and heinoganda explained it in more details. I guess it all depends how paranoid you feel. I think I did manually what this patch does, but i was just tinkering a little bit for fun.