Replies

Morty – As PKCano can explain in greater detail, that MSRT will not work on XP.  It might have run briefly once on PKCano’s virtual XP machine, but that was apparently a fluke, and since then all of us have been getting an error message (which is what we had expected).

But if you also get a fluke run, please take note of exactly what you did and let us know.

2 users thanked author for this post.

Morty, PKCano

PKC – You’ve done something good with mrt (MSRT) that many of us cannot duplicate.  See our struggles at LINK TO MSFN THREAD

Is there anything in your XP that we should know?  Thanks.

PKCano – still no luck.  Could you upload a copy of your file here?  If not possible, maybe to me?  Thanks.

PKCano – You are lucky.  I and a buddy on MSFN only get an error message that it’s not a valid Win32 program.  It won’t install on our XP – POSReady machines.

Did you do anything special?

1 user thanked author for this post.

PKCano – VERY interesting.  How did you run it – quick or full?  Thanks.

Will this latest MSRT (MRT.exe) run on Win XP SP3 that has been kept updated using the POS hack (POSREady 2009 or XP EMbedded)?

Does anyone know?  Thanks.

In a different forum (MSFN), a few folks think this problem with KB 4018556 in XP Embedded (XP continuing to get updates with the POS Ready 2009 hack) might be in the Russian version only (or, who knows, maybe only in the Moldovan version).

On the other hand, MS has pulled it from XP Embedded, so maybe it’s not limited to Russian version only.

Anyway, it’s just a thought.  Anyone who finds out for sure, please let us know.

Спасибо, и повеселились в Молдове.

PS – I’ve kept XP updated on one of my machines because:  all of my emails are there in Outlook Express going back to 1942, no later version of Windows has OE, and it’s just too danged hard to move all of them to a different email app in Win 7 or later.  And updating XP is fun.

Edit Please follow the –Lounge Rules– no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

And Belarc Advisor also shows the same ten standalone security updates as installed last night.  So just maybe I’ve put myself into Group B successfully.  (But in the end, how will we ever know?)

FYI – Belarc also shows the Sept 2016 rollup KB3185278 as installed two nights ago on May 15, 2017.  This makes sense because I UNinstalled all the following rollups that night, and so (I am guessing) the immediately preceding rollup is automatically reinstalled (or maybe just re-disclosed from hiding).

Took my Win 7 64-bit PC offline, UNinstalled the ten Group B security updates I listed a few posts above and then REinstalled them.  They all now show in “View Update History” and “Installed Updates” with last night’s date.  However, they do NOT show in a new MBSA scan.  Instead, MBSA lists one missing update:  KB 4019264 2017-05 Security Monthly Quality Rollup, which I am avoiding as a born-again Group B person.

So MBSA pushes the rollups and skips some (related?) individual security updates.  Bad show.

PK – Yes, understood, and thanks for your infinite patience.

My concern is only that, after I UNinstalled various rollups, MBSA does NOT show as “installed” the seven latest standalone Group B security updates.  My own Windows Update “installed” list shows these seven, but MBSA does not.

And I am unable to REinstall those seven.

EDIT – PK – Ran an MBSA (report attached as a .docx) but I am worried about the results.

1)  It says I am Missing   2017-05 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4019264)   Critical.  This was expected.

2) … but it does NOT list ANY of the seven standalone security updates I mentioned above as being installed.  (From 3212642 to 4019263).  This was NOT expected and is worrying.

So, do I need to install the KB4019264 2017-05 Security Monthly Quality Rollup just to be sure?

Thanks.

PK – Just FYI that I ran MBSA (full report attached as a .docx) and it shows only that I am …

Missing  2017-05 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4019264)

So that looks good, I assume.  (Full report attached.)   Thanks.

pk – thanks twice.

But is there any safe way to test?

OK – I went nuts to backtrack and UNinstall rollups and reinstall security standalones to follow Group B.  Please take a look at the following sequence and confirm I’m OK (or not).  Windows 7 64-bit, and in the past I had installed both some of pkcano’s security standalones and some rollups.  I’m skipping “KB” to save time:

Tonight, I proceeded in this order and got certain results in this order:

UNinstalled rollup 4012215
Installed standalone 3192391
Installed standalone 3197867
Installed standalone 3205394
Then realized my UNinstall of rollup 4012215 probably revived earlier installed rollups, so I looked and UNinstalled more rollups in this order (using cmd wusa /uninstall /kb:xxxxxxx):
UNinstalled 3212646
UNinstalled 3207752
UNinstalled 3197868
UNinstalled 3185330
Then tried to reinstall these older standalones from pkcano’s list at top here – which I had previously installed at various times before today – BUT my PC said each of these was already installed and so I could not reinstall them:
3212642
4012204
4012212
4014661
4015546
4018271
4019263

SO my issue is this:  These final pkcano-security seven – which I had installed in the past and cannot reinstall today – are they really still installed even though tonight I UNinstalled some rollups that might have “included” them?  These seven do still show up as installed in the Windows Update installed lists as of their original (past) install dates AND same on Belarc Advisor.

Can I sleep soundly?  Or am I doomed?  Thanks.

Wall Street Journal has just now published a top-front-web-page article captioned “Major Cyberattack Sweeps Globe, Causing Disruption”.

It’s at this link :  LINK

If we’re on Plan B, are we protected?