Posted on January 30th, 2015 at 11:26 No comments
If you think Win10 builds 9933, 9934 are imminent, I have some sobering news.
InfoWorld Tech Watch.
Posted on January 29th, 2015 at 11:14 4 comments
I think you’ll be surprised to see the dek on this post:
With a few small steps backward and some giant leaps forward, Windows 10 is shaping up as a worthy successor to Windows 7
Yep, you read that correctly. Win10 is shaping up to be downright usable. Still too early to know for sure, of course, but the chicken entrails are starting to line up.
Posted on January 28th, 2015 at 20:34 13 comments
The two caveats:
If you use Excel macros, you’re better off avoiding the December patches KB 2726958 for Office 2013, KB 2553154 for Office 2010, and KB 2596927 for Office 2007. Microsoft still hasn’t fixed the bug that breaks various aspect of Excel macro programming and execution, although it has issued a manual fix: KB 3025036.
If you have an ASUS, Dell, or HP machines, check and see if it’s running an AMD processor. If so, Susan Bradley at Windows Secrets Newsletter — who’s my go-to authority on the subject — advises that you avoid KB 3004365, the January Windows Error Reporting fix.
With those two exceptions, Microsoft has either pulled or fixed all of the outstanding patches, as best I can tell. It looks like Avast has fixed whatever was dogging KB 3000850, from November, and the other problems mentioned earlier don’t seem to be generating the level of screams they once did.
I’m moving us down to MS-DEFCON 4: There are isolated problems with current patches, but they are well-known and documented here. Check this site to see if you’re affected and if things look OK, go ahead and patch.
My usual boilerplate advice:
For those of you who are new to this game, keep in mind that… You should always use Windows Update to install patches; downloading and installing individual patches is a clear sign of impending insanity. I always install Windows Defender/Microsoft Security Essentials updates as soon as they’re available – same with spam filter updates. I never install drivers from Windows Update (in the rare case where I can actually see a problem with a driver, I go to the manufacturer’s web site and download it from the original source). I almost never install “Recommended” patches (reader Marty suggests that you uncheck the Windows Update box that says “Give me the recommended updates the same way I receive important updates”). If Windows Update has a patch but the box isn’t checked, DON’T CHECK THE BOX. It’s like spitting in the wind. I use Chrome and Firefox, and only pull out IE when I feel very inclined — but even if you don’t use IE, you need to keep up with its patches.
Posted on January 28th, 2015 at 11:58 No comments
In spite of WIMboot.
Posted on January 28th, 2015 at 07:21 1 comment
For those of you who are still holding off on installing the December and January patches…
Except for a few known problems, they’re looking OK. I’m going to wait and see what Susan Bradley says on Thursday in Windows Secrets Newsletter before giving a blanket go-ahead with warnings.
The warnings will likely include as-yet-unresolved problems with Excel macros and several others.
Let’s see how it shakes out. In the interim, rest assured that, unless you have state secrets or your work for a foreign intelligence organization, you don’t have much to worry about — there aren’t any mass clobberings going on with the December and January patches.
Keep your powder dry and use Firefox or Chrome…
Posted on January 28th, 2015 at 07:12 No comments
I haven’t seen this problem – or its solution – documented anywhere. Kinda cool.
InfoWorld Tech Watch
Posted on January 27th, 2015 at 11:56 11 comments
Just in from Randy the Tech Professor…This year is off to a big start! TWO Adobe Flash patches, an Adobe Air patch, and of course an Oracle Java patch. The remaining patches are for Chrome, Firefox, Thunderbird, and Seamonkey.Here is the link: http://randythetechprofessor.
com/third-party-program- updates-for-the-month-of- january-2015
Posted on January 26th, 2015 at 21:16 1 comment
Just got this message from John H:
You probably remember how I pestered you about my Windows Explorer crashing every time I right-clicked on it to bring up a context menu. Well, problem solved and you are not going to believe what caused it.
It was Spybot Search & Destroy. That’s right, one of my favorite “indie” tools for fighting obnoxious tracking and spyware. I was having trouble updating it and ran across the following whilst looking for a solution:
An entry in the thread confirmed that the free version also suffers from this bug.
No wonder I couldn’t find what was causing my Windows Explorer to crash! I installed this version of Spybot right after the December patches. It never occurred to me that it could be the problem.
Fortunately, the work-around did the trick. But I can’t help wondering how many other people might be affected by this bug since SS&D turns on the WIN Explorer Integration automatically when you install it.