Category Archives: Windows 10

Ed Earns Windows Insider MVP January 2018

On January 2, 2018, I received email notification from Joe Camp at Microsoft. It informed me that I was named a Windows Insider MVP for 2018. This comes mostly thanks to my good friend and frequent-coauthor, Kari Finn, who nominated me in 2017. But also, thanks to everyone who helped make “Ed Earns Windows Insider MVP January 2018” possible.

This award qualifies me to attend the next annual MVP summit in Redmond. It also gets me a variety of goodies, including free one-year Visual Studio Premium and Office 364 E3 subscriptions. But beyond those much-appreciated perks, I’m both honored and pleased to join the ranks of the Microsoft MVPs. I know well many of them well, and have followed and respected their work since this program kicked off in 1999. I’m especially grateful to MVPs Tom and Deb Shinder, Joli Ballew, Jerry Honeycutt, Shawn Brink, Robert Smit, and my friend and co-author Kari Finn.

Read more about the MVP award and its many distinguished holders on Microsoft’s “Most Valuable Professional” page. To learn more about Windows Insider MVPs in particular, and search their ranks, visit Windows Insider MVPs. To my amazement, I see there are over 150 such MVPs for Windows 10, not counting this year’s new admits (like me).

Windows Insider MVP logo

Thanks to the award, I’m allowed to use this logo for blog posts, email, and business cards.

But Wait, There’s More…

This same month — January, 2018 — also sees the launch of the website Win10.guru. Created in partnership with my friend and fellow Windows Insider MVP and co-author, Kari Finn, we plan to provide oodles of online content that includes how-to and other stories, editorial opinion pieces, and more. We will focus primarily on the needs of IT Professionals and power users who work with Windows 10 both professionally and seriously. Please check out this new site and, while you’re there, share your feedback and requests for coverage with us. Thanks!

Facebooklinkedin
Facebooklinkedin

Oh my! AOMEI OneKey Recovery Gets Interesting

I’ve been working with and learning about recovery partitions on Windows boot/system disks lately. My explorations led me to a decent but flawed tool that does some nice things for Windows OS recovery. It’s called AOMEI OneKey Recovery, and it’s available in both free and commercial versions. In theory, installing this program is easy. You must make space on your system/boot drive. Then, AOMEI OneKey Recovery adds partitions to that disk for boot-up and repair. As a bonus, its recovery partition incorporates a backup of your Windows OS partition. But in practice, AOMEI OneKey Recovery gets interesting. It’s particularly so when it comes to sizing the disk space that the program needs for its partitions. Here’s what the nominal 256 GB SSD drive on my Dell Venue Pro 11 7130 looked like when the program finished its work:

AOMEI OneKey Recovery Gets Interesting

Alas, considerable trial and error was required to properly size the F: partition I had to give AOMEI OneKey Recovery to work with.

Lack of Sizing Data Means AOMEI OneKey Recovery Gets Interesting Indeed!

To begin with, the program provides no guidance on how to size the partition from which it will create its partitions. These are labeled AOMEI and AOMEI Recovery Partition in the preceding screen capture from the Disk Management utility. I started small (at around 2 GB), and went through too many muffed attempts last night. I got increasingly vexed as I kept upping the size of the F: partition that OneKey Recovery used for the AOMEI partitions shown. For each try, I had to use MiniTool Partition Wizard to reduce the size of the C: partition. Then I used that space to expand the F: partition. Things didn’t work until the F: partition hit 44 GB in size. Finally, it created the disk layout depicted in the preceding graphic.

The problem was, resizing the C: partition requires a reboot to do its thing. For each attempt, I used MiniTool Partition Wizard to shrink the C: partition. Then I could grow the F: partition by the same amount. Each iteration took 3-4 minutes to complete because of the time involved in shifting partition boundaries and waiting for the reboot to complete. By the time I’d done this five times I was ready to spit nails. Surely AOMEI could expend the programming effort necessary to analyze the files on the C: partition and estimate the partition size needed to accommodate them? I would have been much happier with my experience in using the software if I didn’t have to keep repeating my attempts to set up those pesky partitions.

It’s Not All Tar and Feathers, However…

To give credit where it’s due, AOMEI OneKey Recovery was reasonably well-behaved aside from the lack or partition sizing information or guidance. It added itself nicely to my Boot Configuration Database (BCD data) on the Dell Venue Pro 11. Better yet, it didn’t mess with the Macrium Recovery Partition already installed on that drive. In testing of its onekey functionality, it worked quite nicely. The program offered to restore my backed-up runtime environment to the C: partition without a hitch. It took about 10 minutes to create the two partitions shown. Thus, I’m guessing it would take about the same amount of time to restore the contents of its Recovery Partition to C:, should that become necessary. I’ll try it out this weekend, when I have some spare time to devote to that task. I’ll follow up with an update then.

On balance I think this is a good tool for a free program. But because it does require resizing of the C: partition to create the space needed for its partitions, a commercial partition manager is needed to put it to work. Not coincidentally AOMEI makes one of those, too. But I prefer MiniTool Partition Wizard, mostly because I already know and understand how to use that program.

Facebooklinkedin
Facebooklinkedin

ExpressCard USB Insights Come Later Not Never

I’ve got a pair of Lenovo laptops I bought in February 2012, as I was preparing to write a book on Windows 8. The book never happened, thanks to an unexpected spate of legal work that year. But those laptops are still kicking and surprisingly capable considering they’re now over 5 years old. One of them is an X220 Tablet with a 12.5″ touchscreen (a very early production touchscreen PC). The other is a T520 with a 15.6″ 1366×768 display. Both units incorporate a dual-core i7-2640M processor, each with built-in Intel HD Graphics 3000 circuitry. The T520 includes an Nvidia Quadro NVS4200M GPU as well. ExpressCard USB insights come courtesy of the plug-in slot for ExpressCard devices on each machine.

These laptops have been through some upgrades along the way from early 2012 to the present day. Both now incorporate 16 GB RAM (2 x 8GB Patriot Memory PC3-10600 SO-DIMMs). Both now boot from Plextor PX-256M5M mSATA SSDs. In 2014, I purchased a StarTech 2 Port ExpressCard SuperSpeed USB 3.0 Card to endow them with faster USB connections. This last facility provides the subject for today’s blog. That’s because I noticed some important things about working with that adapter as I started prepping for the upcoming Windows 10 Creators Update. (It’s due to make its public debut on 4/11/17, but is already available in ISO form to Insider Preview members like yours truly).

ExpressCard USB Insights

For under $30 (Newegg) this plug-in ExpressCard brings two USB 3.0 ports to older laptops like mine. It also comes with a couple of interesting “catches.”

ExpressCard USB Insights Come As I Prep PCs for Win10 Creators Update

In prepping my PCs for the upcoming upgrade, I’m performing a raft of housekeeping tasks, including:

1. Running Disk Cleanup in admin mode, to clean up system files and such
2. Running DriverStore Explorer (aka RAPR.exe) to remove outdated or obsolete device drivers
3. Using the DISM command to clean out the component store with the /startcomponentcleanup /resetbase options
4. Running HomeDev’s excellent PatchCleaner utility to clear out obsolete or orphaned entries from the Component Store
5. Performing complete image backups using Macrium Reflect. Thus, I can easily roll back to 1067.14393.969 or .970 if something goes wrong enough with the upgrade for Windows rollback to fail.

In working with the Lenovo units, I attempted to switch the StarTech card from the 520 to the X220 Tablet while those machines were running. Alas, the USB 3 devices (flash drives and external disks) weren’t recognized at run-time. Further investigation turned up a Device Manager error: “a driver is missing or not completely installed.” To answer the question “Can I plug in or unplug these devices at runtime?” I tried inserting and removing the card on each laptop.

Curiously, the X220 Tablet requires that the card be inserted at boot-up to be recognized and used. But the T520 recognizes the card (with USB drive(s) already inserted) when inserted at run-time. Neither unit allows a USB device to be unplugged. In fact, using “Safely Remove…” to do this properly only shows an option to eject the StarTech card completely. It’s labeled as “Eject USB Root Hub (xHCI).” I also had to close all open applications accessing devices plugged into the card, before it could be ejected. A considerable amount of time, trial, and error is what helped me develop my ExpressCard USB insights, such as they were.

Where’s the “Mount” Option for ISOs?

Another interesting factoid: the “Mount” option that appears in most PCs with built-in USB 3.0 interfaces when one accesses a folder with an ISO file present does not appear in File Explorer in either Lenovo laptop. This fails to appear when a USB 3.0 drive is plugged into the StartTech USB 3.0 adapter. Curiously enough, that same option is also missing from the right-click menu when the same UFD goes into a USB 2.0 port on those machines.

That said, I get the right-click “Mount” option for the very same UFD on all of my other PCs, laptops and tablets.. But then, all of them sport native USB 3.0 ports of some kind or another. When this option is missing, however, one can still use the PowerShell command called “Mount-DiskImage.” This makes an ISO show up as a virtual DVD in File Explorer, as recounted in this TechNet Windows IT Center article (last updated 3/8/2017 as I write this blog post).

{Note added 12/18/17: My friend and colleague Kari Finn points out that you can also mount an ISO on any Win10 system by right-clicking the ISO file and using the “Open with …” option from the context menu. Selecting “File Explorer” when the target is an ISO file also triggers mount behavior. Useful shortcut, actually!}

I have to chuckle that I’ve had this card for three years now, and am just now really learning how it works (and sometimes fails). In acquiring ExpressCard USB insights later is indeed better than never. At least, that’s what the title of this blog post suggests, with tongue planted firmly in cheek. Cheers!

Facebooklinkedin
Facebooklinkedin

Impatience Imperils Progress on 15014 Upgrade

As I was finishing up my day in the office yesterday I made a last pass through TenForums.com. I noticed there that Insider Preview Build 15014 was out. But, alas, I failed to read the covering blog post. Had I done so, I could’ve saved myself some wasted time and effort. Turn out that the progress bar for downloading the latest Upgrade is broken. So when I started updating and didn’t see any progress on my desktop test machine, I immediately presumed “Another issue with WU.” This led to evasive action that ultimately forced me to restore a backup and then reapply the upgrade (successfully) later on. And that’s how I found myself able to observe that impatience imperils progress on 15014 upgrade maneuvers, as noted in this blog post’s title.

You could understand this self-inflicted problem as an “RTFM error,” if you like. But it actually helped me in a couple of interesting and unexpected ways. For one thing, I found myself dealing with the dreaded “black screen of death” on Windows 10. It’s something I’ve read about a lot, but haven’t troubleshot too often. First, I tried to see if the OS was available enough in the background without a working display to launch Task Manager. That meant entering Ctrl-Alt-Esc at the keyboard, then striking Alt-F to open the File Menu. An “R” launches the Run box, which one can use for a variety of tasks. I tried re-launching Windows Explorer, then a shutdown command. Nothing doing. My machine was pretty hosed, it seemed.

Impatience Imperils Progress on 15014 Upgrade

Eventually I did reach my ultimate goal: getting 15014 installed.

Getting Past the Won’t Boot Hurdle

Next, I turned to my old reliable backup program, Macrium Reflect Free. It thoughtfully installs its console as a boot option on the Windows OS boot screen, so I happily fired it off. Inside the Macrium-based Recovery Environment it provides, I found my way to an image of the wonky disk I’d made on January 13. It took just a few mouse clicks to get the restore operation going, and about 10 minutes to complete the job. After that, the machine booted immediately so I could start all over again.

This time, armed with the right information, I let Windows Update chug away to do its thing. This process took around 25 minutes to complete, but the upgrade was entirely successful. Here’s what I learned from this experience:

  • Reading the release notes for a new Insider Build is highly advisable if not downright mandatory
  • Once you’ve started an upgrade, give it plenty of time to run to completion
  • Always keep a current backup available when performing major system changes (like an OS upgrade)
  • If an upgrade fails, be ready to restore that backup and start over, or try again

I did fine on the second two items in the list (I’d learned them the hard way a long time ago). But I’ll have to do better on the first two going forward so I don’t get caught unaware. That’s modern life in Insider Preview land! I don’t want to have to rewrite “Impatience Imperils Progress on 15014 Upgrade” for some other build number, too.

 

Facebooklinkedin
Facebooklinkedin