One year left for Windows 7

Just a reminder that Windows 7 is in its final year of support by Microsoft.

What this means is that as we get closer to the final date [January 14, 2020] and after, companies may stop supporting Windows 7.

This could be anything from no more anti-virus definitions or software updates to no support for new hardware [for example, if your printer dies, there may not be any software that will work with a new printer and Windows 7].

You may also get messages like: “Your browser is no longer supported. Some parts of this web site may no longer work or you may experience problems.”

The above could happened when the various web browsers [Google, Firefox, etc.] stop supporting Windows 7 even though they will support newer operating systems.

What can be done? You can do one of the following:

  • Buy a replacement computer or if you don’t really think you need a computer, buy a tablet [if you don’t have one].
  • Your computer may still be upgradable to Windows 10. There is no cost for the license, but it will be a lengthy process [time and cost] required to migrate.
  • You can leave the computer at is and hope that nothing happens. This means an increased chances of security issues.

More problems with Windows patches

And the “hits” continue. Three new bugs from January 8th batch of updates.

After installing the Windows 7 SP1 cumulative update or the security only update version, those running the Professional or Enterprise version of Windows 7 SP1 may receive a message stating that their copy of Windows is not activated, “counterfeit copy” or “not genuine” if KMS is used. See here for further information.

Windows 8.1 has a bug where after installing the cumulative security update, third-party applications may have difficulty authenticating hotspots. This only is for the cumulative update.  An update is expected later this month.

Windows 10 has the same hotspot bug but only for v1809 and v1709 – not v1803. An update is expected later this month.

There is another bug with the Windows 7 SP1 update [but not confirmed by Microsoft] related to the cumulative update and its security only update where it is causing SMBv2 shares to be inaccessible once it is installed on the host.

There is a further bug with an Office 2010 security update but it only affects Windows XP users. Seriously?  As Windows XP is not supported, don’t expect Microsoft to fix the issue unless it gets fixed in a future update.


Option to delay updates for Windows 10 home users coming soon

Microsoft has been testing the new Windows Update setting in the next edition of Windows 10 preview builds [due in the spring] in the Windows Insiders program. Until then, Windows “Home” users [i.e. those not using the Professional edition, on a domain or and educational edition] can not delay any quality [i.e. non-security and security] updates on their computer.

While Windows 10 Pro and enterprise editions can defer the upgrade for up to 35 days, Windows 10 “Home” users are forced to accept the next quality updates when Microsoft makes it available on Windows Update, whether they want it or not.

Windows 10 Pro and enterprise editions [when not on a domain or centrally managed] can delay feature [i.e. semi-annual] updates for up to a year.

Microsoft has had a bad track record for both quality and feature updates. This would be a welcome for home users. Most issues are discovered within a week.

Those who wish to “upgrade” from Home to Professional can used a previously unused [in Windows 10] Windows 7 or windows 8.1 Professional license or purchase the “upgrade” from Microsoft [estimated around $100 or so].


Microsoft pulls non-security updates for Office 2010

Seems Microsoft is starting off the year on a bad foot just a day before Patch Tuesday. Microsoft pulled all 4 non-security updates released last week even though one may be the culprit. They weren’t taking chances.

Gone are:

  • Update for Microsoft Excel 2010 (KB4461627) – the primary culprit.
  • Update for Microsoft Office 2010 (KB4032217)
  • Update for Microsoft Office 2010 (KB4032225)
  • Update for Microsoft Office 2010 (KB4461616)

At issue is that Excel [and maybe some other Office applications] may crash on start up or have other issues.

Go to “Installed Updates” off “Programs & Features” and remove them.


Windows 10 Fall 2018 Update continues to have issues – now an administrator issue

Even after Windows 10 Fall 2018 Update [a.k.a. Redstone 5, a.k.a. v1809] has been released, it is now known that if you upgrade from v1803 to v1809, the upgrade invalidates the built in Administrator account. The problem seems to occur when the Administrator account is valid and when there are other accounts with Administrator privileges.

At this point, unsure if it will do the same to older version of Windows 10 to v1809. Microsoft says an update at the end of January will correct the problem. Currently the best workaround is to make sure that you have at least one valid account with administrator rights other than the built in Administrator account.

If you have not upgraded to v1809:

  • Right click on This PC in Windows Explorer and select Manage.
  • On the left, click Local Users and Groups and then Groups.
  • Double click on Administrators on the right. Verify there are other accounts in the group other than the Administrator account.

If you have already upgraded to v1809:

  • Right click on This PC in Windows Explorer and select Manage.
  • On the left, click Local Users and Groups and then Users.
  • Double click on the Administrator account and enable it.



Windows 10 October Update available for all

As of today, Windows 10 October [err November] 2018 Update [a.k.a. version 1809] should now available to download an install for anyone.

Generally, Microsoft rolls out feature updates first to highly compatible systems [i.e. those that are quite recent] while they diagnose and try to fix systems that failed to update correctly [from their diagnostics]. So this news is a change and risky.

To manually update, open up the Settings app. Then go to the Update & Security section, and finally check for updates to receive the October 2018 update.

Those who manually update may get the update that may not successfully install.

If you recall in a blog posting back in July, I tried to update my v1709 [October 2017 update] build to the v1803 [April 2018] build and I had issues with my webcam [don’t use much], audio card [I use that!] and the opening screen [just before you log in]. I reverted back to v1709 and have been stuck there ever since. I have Windows 10 Pro. So I can delay the feature update but unsure if I can delay this one now.


Windows 10 October 2018 Update released… with some issues still

So Windows 10 October 2018 Update [a.k.a. Redstone 5, a.k.a. v1809] was finally re-released on Tuesday after about 6 weeks when the original version was released before being pulled.

But not surprising, there are some outstanding issues:

  • When on a network, your mapped drives can’t reconnect at login. See KB4471218 for workaround scripts. An update for this won’t be available until 2019.
  • Some users cannot set Win32 program defaults for certain app and file type combinations using the Open with… command or Settings > Apps > Default apps. [Interesting, as I have something like this in v1709.]
  • Upgrading to v1809 is blocked if you have a AMD Radeon HD2000 and HD4000 series graphics processors. Note that these are unsupported by AMD. Will experience an error in a DLL and performance issues. Microsoft is investigating.
  • When trying to upgrade to v1809 with Trend Micro’s OfficeScan and Worry-Free Business Security software installed, the upgrade is blocked. Trend Micro is to supply a patch.