Tuesday, May 19, 2015

KB3035583 and Windows 10, why you shouldn't install it


No, No, No a thousand times NO!

They're at it again...

In case you didn't notice, an "Important" patch (KB3035583) showed up today or should I say showed up again.  Originally hidden in a batch of updates last April, Microsoft was planning on installing "nag screens" on every copy of Windows from version 7 and above to promote the upcoming release of Windows 10.  Nag screens are bad enough but some clever engineer discovered there was more than just the suggestion to upgrade.   

Of course the description of KB3035583 is dripping with ambiguity meaning most people will just blithely install this latest "important" update without a thought.  

That's a bad thing...

The patch includes not only a series of marketing nag screens but code to install Windows 10 as well.  That's a problem due to the fact that by default many Windows PC's are set to automatically install updates deemed "important" of which KB3035583 is one.  Reportedly, Windows 10 will be distributed similar to the 2014 Windows 8.1 update meaning unless you turn off automatic updates, the upgrade could begin without your knowledge.

But this is all just supposition right? Surely nothing can go wrong with a description like...

" This update enables additional capabilities for Windows Update notifications when new updates are available to the user..."

It's wise practice to question what Microsoft deems "important" and what exactly is meant by "additional capabilities"  especially when those capabilities have the potential to become a pain in the posterior.

Which is why I'm disappointed.  I had hoped that the "New" Microsoft under Nadella would have done away with Ballmer era subterfuge.  Surely the days of clandestine updates that killed off email attachments and upgrade nag screens were over or so I thought.

This latest update lays the foundation for the upcoming Windows 10 rollout.  Yes this latest and reportedly last version of Windows may finally cure the evils of its predecessor but there are still far more questions than answers. 

Questions like, is Windows 10 really free or am I going to get a bill for it in a year.  If I don't want to upgrade immediately what will the "retail" versions cost?  Worse, what happens if I have to reinstall the operating system when it inevitably blows up after the "free" period expires.

For now I suggest that you hide this update.  It's not Microsoft's decision whether or not you upgrade to Windows 10 and you sure as hell don't need to conform to their timeline.


For the next few months keep a close eye on those "Important" Windows updates and if KB3035583 is already installed, remove it.

Thursday, April 2, 2015

Ghosts in the Malwarebytes



Just a quick note.  If you've just suffered a debilitating round of re-installing Office 2003 today ( C'mon now, at least a few of you still have to support it) I may know why.

At roughly 2PM PST on April 2nd 2015,  Malwarebytes released an update (4.2.6) for it's malware scanner  that falsely triggered a quarantine of Microsoft Office 2003 files for a supposed "Trojan.Agent.edt" infection.  The first victim is usually outlook.dll since it's part of Outlook client and the most used application of the suite.  

While the Fortune 500 IT guys may have nothing to worry about here, the rest of us just might.  In the "real" world to find an old version of outlook (like 2003) to be running alongside a newer version of the MS Office suite isn't uncommon.   More often than not small businesses opted to upgrade to a version of MS Office that didn't include Outlook.

That there were more versions of MS Office without it than with was either bad marketing or just a cruel joke.  Regardless, it means you as a small business IT guy or consultant can run into this issue.  

So here are those ingredients for pain again...

You need one part Microsoft Office 2003, one part Malwarebytes and one part bad update.

The fix?

Depending on whether or not the affected system had Office running today the fix is as simple as allowing the latest updates to install (4.3.x).

If, however, you received a feverish phone call toady from users convinced they were experiencing a "Virus!" there's an extra step.

The "infected" office files will be in the quarantine (under the History tab) of the Malwarebytes application.  Select their associated check boxes and simply click "Restore" and answer in the affirmative to any questioning prompt.

You should update the Malwarebytes signature files first, BTW, so that you don't end up in chasing your tail in an endless circle of restoration/quarantine.

The quarantine process removes but does not damage files so their restoration requires no further action to return your MS Office 2003 applications to full functionality.

Follow the steps above and you can consider this bullet dodged.


Check out the video below to see the steps in action!