Woody Leonhard's no-bull news, tips and help for Windows, Office and more… Please disable your ad blocker – our (polite!) ads help keep AskWoody going!
Home icon Home icon Home icon Email icon RSS icon
  • Microsoft fixes the Win10 activation problem

    Posted on November 8th, 2018 at 19:33 woody Comment on the AskWoody Lounge

    My version 1809 test machine was throwing the Activation Error I talked about this morning.

    I followed the updated troubleshooting steps posted by João Carrasqueira on Neowin and, bada-boom bada-bang, it’s all activated now. The Steps:

    1. Click Start > Settings > Update & Security
    2. On the left choose Activation
    3. Under the top section, click Troubleshoot

    Takes all of ten seconds.

    Those of you who paid for a Home license – I suggest you get in touch with Microsoft and yell real loud. They not only owe you a refund, they should pay for the time you wasted fixing their problem.

    If you have any luck with that approach, leave a note here, please. I won’t hold my breath.

    Thx to @EP and Mary Jo Foley

  • A complex solution to the ‘broken file associations’ problem in Win10 1803

    Posted on November 8th, 2018 at 09:09 woody Comment on the AskWoody Lounge

    Remember the bug publicized by Chris Hoffman in Howtogeek on Monday?

    Windows 10 won’t let you make Adobe Photoshop or Notepad++ a default application for images or text files. But you can make other applications, like IrfanView, VLC, or Google Chrome, your defaults…

    our theory is that this stopped working properly when Microsoft released the KB4462919 update on October 9. But we really don’t know.

    PowerShell guru and Admin’s admin Emin has come up with a solution.

    All I did actually is remove anything under the UserChoice, create my own ProgId under the OpenWithProgids key and create its related value under the OpenWithList list.

    … from which springs more than a hundred lines of PowerShell code. (Admittedly, that includes comments. 🙂 )

    P.S. Don’t be put off by “de parvis grandis acervus erit.” The phrase has a fascinating history.

  • Windows 10 Pro deactivates, complains that you need a copy of Home

    Posted on November 8th, 2018 at 06:22 woody Comment on the AskWoody Lounge

    Reports are flying in from all over the world.

    Source: FaiKeeF

    It’s a bug in the Windows Activation server.

    Don’t panic. It’s not your fault.

    Right now, based on personal experience (see below), this activation red herring hasn’t made any difference at all in the way Win10 Pro works.

    Details in Computerworld Woody on Windows.

    Thx @gborn.

    UPDATE: Zac Bowden on Windows Central has identified a possible source of the problem:

    It appears those affected are users who upgraded using older Windows 7 and Windows 8.1 product keys. Devices that shipped with Windows 10 Pro appear to be unaffected at this time.

    Can you confirm?

    ANOTHER UPDATE: Microsoft has elevated the “one or two business days” explanation to a sticky post, adding:

    Edit 1: Users report that Windows activation troubleshooter might say You have a Windows 10 Home license but you are running Windows 10 Pro. You are advised to ignore that message and wait for the fix.

    Methinks the offal has hit the fan. Bet you didn’t know how reliant you are on behind-the-scene activation checks.

    ANOTHER UPDATE: I’d be willing to guess that this bug affects machines that have been upgraded from another version of Windows to Windows 10 Pro. Seeing reports on machines upgraded from Win7, 8.1, and Win10 Home to Win10 Pro. (But note this post from Moltium, which says brand new Win10 Pro 1803 machines are getting hit. Thx Richard Speed from The Register.)

    AND ANOTHER…: I just got this activation error on a Win10 1809 system: