A few days ago, Ed Tittel wrote about Windows Update deleting failed updates, and “banning” those updates for 30 days. That article got me thinking about my personal relationship with Windows, and if I trust it to know how to take care of itself — or not. In my case, the answer is a clear
Two months ago, I posted instructions on how to get the latest Windows 10 Insider Preview Fast or Skip Ahead ring ISO image using UUP Dump. The problem is, UUP Dump only offers ISO images for Home, Home N, Pro and Pro N editions. To get the latest Fast Ring or Skip Ahead ISO images
Having just gone back to check the date, I’m amazed to be reminded the default change to the OS clean-up interval from 30 to 10 days goes back to Version 1607, aka the Anniversary Update. I first wrote about this in August 2016 for my Windows Enterprise Desktop blog at TechTarget. When this release emerged,
If a Windows update, feature, or language pack comes in the form of a CAB file and needs to be applied to a Windows image, DISM /Add-Package will do the job (works for either offline or online images).
The problem with shooting Windows 10 trouble, alas, is often in knowing where to aim. Case in point: my recent Reliability Monitor shows an error from the Windows Shell Experience. The specific error is labeled MoAppHang. As far as I can find out (and additional reporting data confirms this finding) this means some kind of
DISM offers tools to report on the size of the Windows Component Store that also recommend when cleanup is needed. Cleanups can recover multiple gigs of disk space, especially after a cumulative or multiple new Windows Updates.
One potential secret to IT success is careful and judicious use of automation tools and technologies. But remember: automation is supposed to SAVE time and money, not spend it wildly or wastefully!
On my HP ProBook laptop, I’ve had a strange issue regardless of which Windows 10 Insider build I am running: the Hypervisor will be turned off when the laptop is powered off, which makes it impossible to run Hyper-V virtual machines following a cold boot. When the Hypervisor is enabled, it survives restarts but the