Newsletter Archives

  • Got a Western Digital My Cloud device?

    Make sure that you know if you are supported or not – if you still plan to use these devices make sure they are NOT set to have remote/Internet access and are only accessible internal to your home network.


    Support for your My Cloud device is changing
    Western Digital continuously evaluates and improves our hardware, software, and services as security standards evolve. As a result, we’ve determined that it’s necessary to end support for prior generations of My Cloud OS, including My Cloud OS 3. You should act now to protect your content.
    On April 15, 2022, support for prior generations of My Cloud OS, including My Cloud OS 3, will end. Your device isn’t compatible with critical security updates that are only available for My Cloud OS 5-compatible devices. As a result, you’ll only be able to access it locally. After April 15, 2022, your device will no longer receive remote access, security updates, or technical support. To help protect your content, we recommend that you back up your device, disconnect it from the internet, and protect it with a strong, unique password. Check out our recent My Cloud updates to learn more.
    Thank you for being a long-time Western Digital customer. We understand that your content is important to you, and we appreciate that you trust us to help you preserve it. To show our appreciation, we’re sending you a 20% discount coupon in January 2022 that you can use toward an eligible device. Keep your eye out for another email from us with information about that discount. 

    My Cloud Team


  • What would you suggest?

    Patrick writes…..

    At the present, I am running a desktop 11 year old Dell Studio 540 with an Intel Core 2 Quad Q8300 at 2.50 gHz (purchased in 2009). The HDD is beginning to run less than quietly. It is running Windows 10 20H2 (OS Build 19042.964). I just took almost 2 days (not full time, but agonizing anyway) to get iCloud for Windows working again with my Outlook 2016 after a Windows Update.

    When we recently got AT&T Fiber installed, I tried to connect with the Cat 5 cable installed in the house – to no effect, so I added a Mesh system. It works, but the signal is pretty low where the computer is installed.

    Which would be the better choice for me – (1) replace the HDD (I’ve been using a Seagate Portable 2 Gig SCSI disk to image the internal drive which is partitioned into C:,H, and J), or just buy a new computer and start over?

    So what would you do?  I’ll add my recommendation in the comments.

  • Pulling the trigger on Win10 Version 2004



    By Susan Bradley

    Windows 20H2 is in the pipeline — so it’s about time to install … its predecessor, Win10 2004.

    On October 20, Microsoft tweeted that the October 2020 Update (aka 20H2) has been officially released and will show up over time via a “throttled” rollout. But a few of the tweet’s replies quickly noted that some Win10 users are still waiting for Version 2004 — or had to manually install it. (Microsoft states that the upgrade from Win10 2004 to 20H2 should go faster because it’s more like a monthly update.)

    Read the full story in AskWoody Plus Newsletter 17.42.0 (2020-10-26).

  • Patch lady – pet peeves about icons

    For my business needs I have to have Adobe acrobat.  It’s demanded by some of our business applications.

    So when I notice tonight that the icon in my system tray of Adobe’s creative cloud (part of the software subscription suite) changed to a very annoying color, needless to say it’s another time that I ask… so whom did they get feedback from?

    So what annoys you about icons?

  • Determining what’s blocking Windows 10 2004


    By Susan Bradley

    Whenever Microsoft releases a new version of Windows 10, days, weeks, and even months can pass before the upgrade successfully installs on individual PCs.

    Why? Why does Microsoft take so long to fully roll out a new feature release?

    So I wondered: Are there are ways to determine why a machine isn’t qualified for a Windows feature upgrade? The answer in short: There are, but they’re not easy.

    Read the full story in AskWoody Plus Newsletter 17.22.0 (2020-06-08).

  • When Windows 10 Feature Updates don’t go smoothly

    Last weekend, I decided to bite the bullet and update a Win10-1803 Pro machine to Win10-1809, using Windows Update. I’d taken a system image backup, and as it wasn’t my production machine, I wasn’t too worried.

    This machine is under a year old, a purchase necessary when a hardware failure put paid to my trusty Win7 Pro laptop. It allows me to work more than I can manage at my desktop, and does most of the hard yards online, especially here.

    Windows Update installed 1809 x64 2019-10B – this was before Woody changed MS-Defcon from 4 to 2. It took 20 minutes to Prepare to Install, and nearly 2 hours to download, and several hours to install.

    Needless to say, it didn’t go to plan… The first indication of a problem was after several hours of installing, when a blue screen appeared bearing the words “Stopcode” and “Bad Pool Header”. It restarted, still on 1803, pending install. It continued installing. Eventually it restarted, and I was able to see KB 4521862 and KB 4519338 had installed – along with a bunch of drivers being updated, when the Pro settings were not to download drivers from Windows. I also noticed I hadn’t had to reset the Metered Connection settings to allow the update to download!

    After it finished its update, it wasn’t working properly. It looked fairly normal, but restarting started problems – none of the visible desktop items actually worked – not the Start button, any of the TaskBar icons, or anything other than the Ctrl>Alt>Del routine.

    I tried Sign Out. It took ages. It caused a loop of: Hi; We’re getting everything ready for you; This might take several minutes – don’t turn off your PC (that part remained until it got to Hi again); Leave everything to us; Windows stays up to date to help protect you in an online world; Making sure your apps are good to go; It’s taking a bit longer than expected, but we’ll get there as fast as we can. This loop took 5 minutes to restart, again, and again, and again.

    It had been over 12 hours since the process started at this point. As I had to do my day job, I just left it chugging away in the background while I got on with earning an income. Over 5 hours later, it finally came up for air – a desktop, but still not functioning.

    Along the way, I saw various errors:
    Error 0x80072EE7
    The gpsvc service failed the sign-in – access is denied
    windows\system32\config\systemprofile\desktop is unavailable

    To add to my woes, it wanted to restart itself again, where it re-entered the 5+ hour loop. I still had work to get done, so I just let it be. No stopcodes this time, but still it didn’t work.

    I couldn’t access safe mode, even with Recovery Tool USB access. Start Up Repair “couldn’t fix [the] PC”. Using the Recovery Tool, I was able to access the Command Prompt, where SFC /SCANNOW reported “Not enough memory resources are available to process this command” the first time, and then, after it went through 100%, “Windows Resource Protection could not perform the requested operation”. Attempting to use Restore Points was another failure – they were listed, but “unavailable”.

    At this time, I decided it was time to try to restore the system image. Again, the gpsvc error. Apparently there had been some issue prior to the update attempt? I had to put it aside for a few days, until I got time to address it properly. By this stage, I was heading for an ISO file on a USB stick. This laptop now needs to be reset from the ground up, going back over all the metered connection, deferred updates, Customer Experience, Start Menu apps settings etc. etc. etc. – and I’m sure there’ll be something important I forget!

    Having got the ISO installed, I was able to run SFC / SCANNOW and DISM /Online /Cleanup-Image /RestoreHealth. All 100% clear, thank goodness.

    There are only 5-6 programs to reinstall. If this had been a production machine, I’d have dozens of programs to have to reinstall. It’s still going to take another day or two until I get it back to normal, as I have other things I need to prioritize. If I’m a bit cranky this weekend, you now know why!

    I’m really lucky I have a wealth of knowledge, support and expertise here at my disposal. A normal home user would have ended up paying for professional technical support, and if it had been my production machine, would have resulted in a loss of chargeable hours. I’m counting my blessings!

  • Patch Lady – computers know when they are going to be replaced

    There are some fundamental truths in computing.

    1. Computers hear when you talk about replacing them and suddenly start doing weird things.
    2. When you are doing a migration process, do not install updates.

    …so Saturday night at 3 a.m. the server that housed our old (and still active) domain controller went offline.  The time of 3 a.m. is notable as it’s the historical and traditional time that updates are installed in my office.  This server is a virtual machine and was housed along with a few others on an older HyperV server that I’m getting ready to retire.  In a small environment I normally don’t join the HyperV (virtual server) to the domain, but had in this case in order to do a live migration from the old server to the new server.  I was going to leave this one domain controller behind once I migrated off of it on the old server since I was planning to retire it, along with the HyperV.  My guess is that because I had joined it to the domain it inadvertantly caught the update policies from the domain and installed updates that I hadn’t intended and it rebooted.  Note that I can’t prove this, but I just know what I did to the server and how it went offline at 3 a.m on Saturday morning, which is the exact time that updates are normally installed in my office.

    Now comes the fun part.  When I went to the office to see why it wasn’t online, it was at a boot  prompt waiting for a bitlocker key for the C drive.

    Now here’s the thing, when I built this server five years ago I wasn’t comfortable with bitlockering the boot drive so I didn’t do it.  I bitlockered (drive encryption) the Data drive on D, but NOT the C drive.  And I’m positive I didn’t because I blogged at the time (five years ago) that I wasn’t comfortable with encrypting the boot drive.  I had the print out of the bitlocker key for the D drive, but NOT the C drive as I never bitlockered the C drive.  I went back in fact and found my blog post where I talked about not bitlockering the C drive.

    And the bitlocker key wasn’t hooked to a Microsoft account like my Surface devices, nor was it in AzureAD as again, I never entered  it on the C drive.  So the two places that you can go to to see if your bitlocker key is there, I know it wouldn’t BE there.

    Needless to say I didn’t have a recovery key when I never gave it one.   Just for grins I tried the recovery key of the D drive (you can see that above) and it said it was incorrect.  Yeah, no kidding!  So while I then got out my backup of that server and started the process of restoring it to the new HyperV server, I decided to also reinstall the host OS knowing that once I got into the server I could then reset up the HyperV server that was safely on the D drive untouched.  It was an exercise to see which method would be faster and rebuilding the boot drive was faster than the restoration process.

    So what update might have triggered this?  I honestly don’t know.  I know that when I patched this hyperV server based on 2012 R2 I only installed recommended updates not optional ones.  I never installed a later .net.  Given that I had hooked it to the domain, my guess is, and I can see in my WSUS policies that it had picked up additional patch approvals while on the domain and accidentally installed them.  Shame on me I know better than this and while doing migrations I should have turned the windows update service to disabled.

    It’s a reminder to me that encryption is wonderful, until it’s not.  It’s a reminder to ensure you have an alternative way to get to the web because your normal method may be impacted.  It’s a reminder to remember you have backups and to have paper documentation of passwords and information in case you can’t get into the digital copies.  It’s a reminder to download a copy of Windows media and have flash drives and external usb hard drives as supplies ready at a moments notice.

    ….. and finally, it’s a reminder to not talk about new servers and migration plans while the old server is listening.  Clearly I hurt it’s feelings.


  • LangaList: Is high disk usage a RAM problem or a PC problem?

    Another pearl of wisdom from Fred Langa:

    If a PC is running slow despite having reasonably current and otherwise-healthy hardware, then too-little RAM is for sure a prime suspect…  start by loading up on RAM: It’s usually the cheapest, fastest, easiest way to improve performance.

  • Considerations migrating from Win7 to Win10


    By Susan Bradley

    With time winding down on Windows 7 support, more than a few users of that venerable OS are looking for some upgrade clarity.

    Top-of-mind for many Win7 users is how painful it’ll be moving to Windows 10. Are in-place upgrades still legal? Does Microsoft care? Can I migrate to Win10 and keep my current setup? Is it free?

    Read the full story in AskWoody Plus Newsletter 16.32.0 (2019-09-09).