What’s up with the “new” XP patch KB 982316?

Topic

New Reply

I don’t know what to make of it. I’m seeing reports all over the internet that Microsoft has released a new Windows XP patch, KB982316. Yes, Windows X
[See the full post at: What’s up with the “new” XP patch KB 982316?]

Reply | Quote

Replies

This implies it’s been around since 2010, so your thoughts about it being something old that just bubbled up out of the tar pits might be right on.

https://social.technet.microsoft.com/Forums/windowsserver/en-US/a340eee4-0f0a-4a09-9049-0288621825c4/is-kb982316-not-available-for-wsus?forum=winserverwsus

-Noel

Reply | Quote

I just ran Windows Update in my XP (ltsb/POS Ready 2009)/virtual machine setup.  No patch was offered.  As an aside, as of a few weeks ago, XP people are having trouble accessing Windows Update from either the security center or the control panel.  However, XP WU can still be accessed directly from the Internet at this page: http://update.microsoft.com/windowsupdate .  In fact, this will be the only way for one to view past updates, hidden updates, etc. if you are no longer able to access WU from the security center or the control panel.

2 users thanked author for this post.

Cybertooth, woody

Reply | Quote

The digital signature of the downloaded file indicates that it’s still the same old one

“Monday, ‎June ‎14, ‎2010”

 

so just a review/renew of the download page for some reason

1 user thanked author for this post.

woody

Reply | Quote

Just ran Microsoft Update on two XP/SP3 machines. No new updates.

GaryK

Reply | Quote

Slightly OT, but Microsoft just added a new Malicious Software Removal Tool update (KB890830) for Windows 8.1 and 7 dated 5/22/17

It was marked “Important”, but not sure what it cures.

 

 

Reply | Quote

Also for the other Windows-versions:

Windows 10,Windows 10 LTSB,Windows 8,Windows 8.1 Rollup n.v.t. 49,3 MB
Windows Malicious Software Removal Tool for Windows Insider Preview – May 2017 (KB890830) Windows 10 Rollups n.v.t. 49,3 MB
KB890830: Windows-programma voor het verwijderen van schadelijke software – mei 2017
Windows 7,Windows Server 2008 Update Rollup n.v.t. 49,3 MB
Windows-programma voor verwijderen van schadelijke software voor Windows 8, 8.1, 10 en Windows Server 2012, 2012 R2, 2016 x64-editie – mei 2017 (KB890830)
Windows 10,Windows 10 LTSB,Windows 8,Windows 8.1,Windows Server 2012,Windows Server 2012 R2,Windows Server 2016 Update Rollup n.v.t.50,5 MB
Windows Malicious Software Removal Tool for Windows Insider Preview and Server Technical Preview x64 – May 2017 (KB890830)
Windows 10,Windows Server 2016 Update Rollups n.v.t. 50,5 MB
KB890830: Windows-programma voor het verwijderen van schadelijke software voor x64-systemen- mei 2017
Windows 7,Windows Server 2008,Windows Server 2008 R2 Rollup 22-5-2017 50,5 MB

EDIT major editing from html to text was required on this post, so it may not read as intended. Pls note the information here about posting limitations – we aren’t always able to salvage html posts for publishing.

Reply | Quote

Sorry, I sort of got tangled in the tables 🙁 Wanted to show that all versions have a new MSRT, all dated 22 May. Which is Out of Band, so wondering what is going on.

1 user thanked author for this post.

Kirsty

Reply | Quote

It is possible that the MSRT scanner has been updated to detect WannaCry and due to the urgency of the situation, was released out of band.

1 user thanked author for this post.

woody

Reply | Quote

Yes, you’re right. Just read this on https://blogs.technet.microsoft.com/msrc/2017/05/12/customer-guidance-for-wannacrypt-attacks/

Update 5/22/2017: Today, we released an update to the Microsoft Malicious Software Removal Tool (MSRT) to detect and remove WannaCrypt malware. For customers that run Windows Update, the tool will detect and remove WannaCrypt and other prevalent malware infections. Customers can also manually download and run the tool by following the guidance here. The MSRT tool runs on all supported Windows machines where automatic updates are enabled, including those that aren’t running other Microsoft security products.

 

Mystery solved.

1 user thanked author for this post.

radosuaf

Reply | Quote

Can’t believe Microsoft is still fiddling with XP at all?

Reply | Quote

XP Embedded is supported until 2019.

Fractal Design Pop Air * Thermaltake Toughpower GF3 750W * ASUS TUF GAMING B560M-PLUS * Intel Core i9-11900K * 4 x 8 GB G.Skill Aegis DDR4 3600 MHz CL16 * ASRock RX 6800 XT Phantom Gaming 16GB OC * XPG GAMMIX S70 BLADE 1TB * SanDisk Ultra 3D 1TB * Samsung EVO 840 250GB * DVD RW Lite-ON iHAS 124 * Windows 10 Pro 22H2 64-bit Insider * Windows 11 Pro Beta Insider

Reply | Quote

April 9, 2019 to be exact, radosuaf

Reply | Quote

I don’t mean to be critical, but what’s interesting is that idle comments like “Can’t believe Microsoft is still fiddling with XP” may be influencing them into making some very wrong choices and shorten support periods of operating systems going forward, or at least commit to support less strongly.

Do you really want people to be forced to change out something that works for a particular purpose just because the maker chooses not to “fiddle” with it any longer? Put another way, do you think an “operating system as a service” model is realistic?

Serious people in the past wouldn’t choose to use a product that’s critical to their business without a strong promise of support. Whether support is something Microsoft can just choose not to commit to any more and get away with it remains to be seen. There are big, subtle concepts in play here.

We should be thankful that Microsoft continues to “fiddle” with XP and release nice patches for people still using it. Your local ATM machine may still be running XP embedded, and somehow I think you’d probably rather a ransom not be drawn directly from your account.

-Noel

2 users thanked author for this post.

Morty, Elly

Reply | Quote

Noel Carboni wrote:

I don’t mean to be critical, but what’s interesting is that idle comments like “Can’t believe Microsoft is still fiddling with XP” may be influencing them into making some very wrong choices and shorten support periods of operating systems going forward, or at least commit to support less strongly. Do you really want people to be forced to change out something that works for a particular purpose just because the maker chooses not to “fiddle” with it any longer? Put another way, do you think an “operating system as a service” model is realistic? Serious people in the past wouldn’t choose to use a product that’s critical to their business without a strong promise of support. Whether support is something Microsoft can just choose not to commit to any more and get away with it remains to be seen. There are big, subtle concepts in play here. We should be thankful that Microsoft continues to “fiddle” with XP and release nice patches for people still using it. Your local ATM machine may still be running XP embedded, and somehow I think you’d probably rather a ransom not be drawn directly from your account. -Noel

It would be nice if we could influence them, but Microsoft stopped listening to us a while ago.

GaryK

1 user thanked author for this post.

ch100

Reply | Quote

No, I think they’re listening to the masses a little too much. It’s an operating system, not a facebook page.

-Noel

3 users thanked author for this post.

Morty, Elly, ch100

Reply | Quote

Please stay on topic. The topic here is the “new” XP patch KB 982316

Reply | Quote

Sorry, clicked the wrong button and I cannot withdraw the misplaced Thanks now. 🙁

Reply | Quote

woody

KB982316 is only available from the MS Download Center. I think MS just re-posted the XP version of it there on 5/19/2017 after removing it in early 2016.

All the other versions of KB982316 (for Server 2003 and later) are dated 8/9/2010.

2 users thanked author for this post.

Morty, PKCano

Reply | Quote