News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • Microsoft unexpectedly declares Win10 1809 ready for business

    Posted on March 28th, 2019 at 13:13 woody Comment on the AskWoody Lounge

    This with a list of acknowledged bugs almost as long as my arm.

    Details in Computerworld Woody on Windows.

    Yeah, I think somebody read Susan’s Hey 1809, we need to talk.

  • Report of Win10 version 1903 upgrade trashing an SD card

    Posted on March 28th, 2019 at 09:48 woody Comment on the AskWoody Lounge

    I’m emphasizing this to see if anyone else has hit the same problem.

    @GreatAndPowerfulTech reports that installing the 18362 build of Win10 version 1903 trashed all the data on his SD card, and re-assigned the drive letter.

    Isolated incident, or harbinger of an 1809 redux?

  • Tell Microsoft what you think of their (greatly improved) update history pages

    Posted on March 28th, 2019 at 08:05 woody Comment on the AskWoody Lounge

    When I originally saw this, I ignored it.

    Microsoft knows what I feel about the Windows update “experience.” In a nutshell: Way too many, poorly tested, utterly mis-managed, disastrous. Win10 1809  may finally be breaking the downward spiral, but it’s too early to tell.

    At Susan’s urging, I took another look at Dona’s request. The questionnaire isn’t about the infernal Windows update experience. Microsoft is asking questions about the Windows update history site. That’s a horse of a completely different color.

    Truth be told, I’m a huge fan of the massive improvements in patch documentation. In the past six months, Microsoft’s gone from obfuscation and dodging to something approaching openness and honesty. The lists of individual patches is a joke – there are so many of them that your scorecard needs a scorecard. But the update history pages are, suddenly, quite worthwhile.

    Your opinion may vary, of course, which is why I urge you to take the survey.

  • Somebody took over my dormant Google account. What should I do?

    Posted on March 28th, 2019 at 04:32 woody Comment on the AskWoody Lounge

    This is a real-life problem.

    Several years ago I registered a domain, woodyswindows.com. I set up some email addresses using that domain, but didn’t do anything else with it. A couple of years ago, I let the domain registration lapse.

    Yesterday I got a notice from Google that my woody@woodyswindows.com account had been recovered:

    Shortly after, I was informed that somebody had changed the recovery email for woody@woodyswindows.com.

    Naturally, I clicked the Check activity link. I was asked to log in to my Google woody@woodyswindows.com account – and at that point I discovered that I didn’t have the password. Either I forgot it (unlikely) or it had been changed. Er, recovered, I guess.

    Somebody managed to take over my old (dormant) Google account, change the password, and lock me out of the recovery email. And I can’t get in to change anything back.

    Any advice? woodyswindows.com is deader ‘n a doornail. Is this worth pursuing? If not, why not?

  • TechCrunch: ASUS was warned of hacking risks months ago, but did nothing about it

    Posted on March 28th, 2019 at 03:51 woody Comment on the AskWoody Lounge

    A fiery condemnation from Zack Whittaker at TechCrunch:

    A security researcher warned Asus two months ago that employees were improperly publishing passwords in their GitHub repositories that could be used to access the company’s corporate network.

    One password, found in an employee repo on the code sharing, allowed the researcher to access an email account used by internal developers and engineers to share nightly builds of apps, drivers and tools to computer owners.

    This specific security breach wasn’t directly responsible for the ShadowHammer infiltration, but it demonstrates an incredible lack of concern over simple security procedures.

    Günter Born has additional analysis on his site.

  • Patch Lady – Hey 1809, we need to talk

    Posted on March 28th, 2019 at 00:25 Susan Bradley Comment on the AskWoody Lounge

    I posted this earlier to the Patchmanagement.org listserve and was urged by Crysta to post it here as well.

    Dear 1809. You are about to be replaced in the hearts and minds of patchers by your younger version 1903. And yet you keep acting like you aren’t ready for business.

    Take your March patching release. All your other older brothers have had a preview release come out on the C week (third Tuesday). You however, have been aloof and haven’t released your C/D week update this month. Last month you released your C/D week for February in the month of March.

    So can we settle down and act like you are ready for Business please? You promised a fix for the Audio bug introduced earlier this month. “Microsoft is working on a resolution and estimates a solution will be available in late March 2019.” Well it’s late March and still no fix.

    My big beef with your tardiness is that it makes determining when a zero day patch has been released harder. Please settle down and release your updates on Tuesdays, along with your older brothers. Thank you.

    (Seriously, it’s now the final week of March, and we’re past the Tuesday of the D week slot.  Releases need to be consistent in their release schedules otherwise it gets confusing to tell what is a zero day release.  The D week releases normally aren’t pushed but if you “seek” updates, that is click on windows update and then check for updates, you would get these D week ones.  I rely on the Windows update history pages and I’ll be giving feedback to Dona that they are used and some weeks I’m going to them on a daily basis to see what’s up.)