Jump to content

How about MS17-010 / wannacry on Windows 2000


 Share

Recommended Posts


  • 2 weeks later...

> it based on 5.0.2195.7365
Why is it 5.00.2195.7367 and why is it based on 5.0.2195.7365 instead of 5.00.2195.7369 (Windows2000-KB2508429-v12-x86-ENU)?

> and backport from MS16-114 to MS17-010 fix only
This doesn't make sense because MS16-114 is older than MS17-010 and doesn't contain the MS17-010 fix.

Link to comment
Share on other sites

7 hours ago, jumper said:

> it based on 5.0.2195.7365
Why is it 5.00.2195.7367 and why is it based on 5.0.2195.7365 instead of 5.00.2195.7369 (Windows2000-KB2508429-v12-x86-ENU)?

> and backport from MS16-114 to MS17-010 fix only
This doesn't make sense because MS16-114 is older than MS17-010 and doesn't contain the MS17-010 fix.
 

I dug in msfn and found this:

and this may be why blackwingcat NOT to use 5.00.2195.7369.

But what about Windows2000-KB2508429-v17(5.00.2195.7371)?

Edited by roytam1
Link to comment
Share on other sites

On 2017/5/25 at 0:30 AM, roytam1 said:

I dug in msfn and found this:

and this may be why blackwingcat NOT to use 5.00.2195.7369.

But what about Windows2000-KB2508429-v17(5.00.2195.7371)?

I do not know 5.00.2195.7369. 's BSoD bug fixed whether or not, so I uses 5.0.2195.7365 :3 (Perhaps that was WildBill's update.)

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.


×
×
  • Create New...