On December 8, Microsoft released its first major Windows 10 build using the new Unified Update Platform. So far, many users — including yours truly — experience Download hanging at 0% progress. MS has issued a workaround that lets users download despite that difficulty. Unaware that the problem was widespread, I immediately tried the Windows Update MiniTool when I got stuck myself. I’m pleased to report that WUMT works with UUP, and grabbed the update for installation without a hitch. In fact, I experienced my fastest ever download times using the tool yesterday, hitting a whopping 450 Mbps on my putative 300 Mbps connection.
Though WU got stuck, WUMT happily downloaded — and starting installing — Build 14986.
[Click image to see full-size version.]
What WUMT Works with UUP Means
Aside from the obvious — that WUMT works quite happily with UUP — this informal test tells us that the internal mechanisms for UUP don’t alter Windows Update deliver fundamentals. I’d been wondering if UUP would change things enough to make WUMT fail. It’s nice to see it continue working in the face of changes to Windows Update behavior. We know that UUP checks the manifest of installed updates on PCs requesting them. It sends only missing items in response. It’s great that these changes don’t keep WUMT from working.
I had already recommended WUMT as a Windows Update replacement and reported that WUMT Does Updates When WU Can’t or Won’t in earlier blog posts here. It tickles me that WUMT keeps on ticking, even as UUP makes the scene.
[Note: I recommend the download link for WUMT from MajorGeeks.com. Its anonymous creator, Mr. X, first published this work on the Wilders Security Forums in October 2015. Apparently, Mr. X is a Mexican software developer: his identity is tied to website ru-board.com, but the Wilders link to his account is no longer live. I’ve been using this tool for several months now, despite its deliberately shrouded origins, and have found it to be fast and capable. Would that all freeware were this good.]
Microsoft’s declaration in November that the latest version of Windows 10 is enterprise-ready created confusion in some businesses that had already been using it for months.
After Microsoft releases a Windows 10 Anniversary Update, as it did in August, the company spends 90 days noting and responding to all the issues customers and independent software vendors have. IT experts who were not aware of this process said they’d like better communication from the vendor.
“Microsoft has always done a poor job of communicating this kind of stuff,” said Doug Grosfield, president and CEO of Five Nines IT Solutions, a Microsoft partner in Kitchener, Ont. “And then there is always a cleanup operation involved. It’s unfortunate for the customer and creates extra work.”
For example, Grosfield’s customers faced issues with VPN client software from providers including Dell, Cisco and SonicWall. Following the installation of the Windows 10 Anniversary Update, some businesses needed to reinstall their VPN client software for them to work again, Grosfield said. Initially, this caused many problems and halted productivity for remote workers.
Microsoft should have addressed these and other issues and labeled the Windows 10 Anniversary Update as enterprise-ready when the company released it, Grosfield said.
“Microsoft has got some ground to make up on the Anniversary Update because it was released in a way that broke a lot of things,” he said. “It would take hours to actually do the update, which was very disruptive, and it created some problems to solve with a bunch of software.”
The Anniversary Update also caused problems for many antivirus software platforms initially, but they have since been resolved.
It’s always a good idea to wait to install any software update because of situations like this, where the update causes problems with other software or has its own bugs, said Robby Hill, founder and CEO of HillSouth, an IT consultancy in Florence, S.C.
“It’s been a best practice in IT services for quite a while,” Hill said.
In early November, I blogged about Microsoft’s Unified Update Platform (UUP). In that post, I reported that Insider Build 14959 would include UUP features and functions starting with Mobile releases. Last Friday, Insider manager Dona Sarkar shared more news as UUP starts getting real. Here’s a quote from her Windows Insider Program post “Announcing Windows 10 Insider Preview build 14977 for Mobile”
We are getting ready to start releasing PC builds to Insiders using UUP. To prepare for this, we are going to pause all PC builds for both the Fast and Slow rings starting this evening (Friday 12/2). We will begin flighting the latest builds via UUP starting with our internal rings first then to Insiders based on each ring’s promotion criteria. We’re excited to be able to release builds for PC to Insiders using UUP! Mobile builds are not impacted by this.
The switch to UUP represents a nuts-n-bolts shift for Windows Update.
When UUP Starts Getting Real, What Can We Expect?
Under the hood, MS is changing how it structures updates. At present, MS releases cumulative updates monthly. That means such updates include roll-ups of all Windows 10 updates released since the last major release milestone. That way, users updating a newly installed OS need apply only the most recent cumulative update. In any given month, whatever other security, malware scanning, and other updates released since the cumulative roll-up also apply. And in fact, MS plans the same approach for future Windows 7, 8, and 8.1 updates.
How does UUP change things? Essentially, it checks the manifest of updates already applied in the requesting Windows image against its update database. Then, it transmits only missing items from its WU servers. Rightfully so, MS calls these items “differential downloads” or “delta updates.” (This draws on database and change management terminology.) Thus, MS predicts that UUP decreases download data volume as much as 35%. This in turn means faster downloads and less overall bandwidth consumption. Most computer trade reports on UUP view it positively. For example, PCWorld states “… it’s pretty obvious the experience of downloading and installing new updates from Windows should be vastly improved by its [UUP’s] adoption.”
But as with many new MS technologies that promise improvement, the jury’s still out. Let’s see if they can indeed deliver on those promises. Windows Update has been a major pain for many Windows 10 users recently. An actual improvement could help kill that pain. Here’s hoping it pans out! Once Insider Preview releases resume, the world will find out. Stay tuned for my follow-up reports.
The long tail is a concept popularized in the early 2000s by writer Chris Anderson, who first used the term in an eponymous Wired magazine story. Simply put, the long tail concentrates on the tail end of certain statistical distributions (such as the Zipf, power law, and Pareto distributions). This might sound a bit ivory tower. But it explains how large populations shake out into small clusters of elements at their tail ends. Companies grab this tail to expand their ability to sell more into a market. How Windows 10 PC’s organize themselves by the devices and chips they contain is similar. My growing belief is that for Microsoft, the long Win10 tail carries a nasty barb or two. In fact, it’s stinging them soundly right now.
The distribution of who’s using what kind of PC hardware also fits this curve, and things happening to users on the long tail are biting Microsoft these days.
Why See Barbs on the Long Win10 Tail Anyway?
I’ve been looking for a way to explain numbers of unhappy Windows 10 users who pop up on public forums such as answers.microsoft.com, and TenForums.com. Many of these users report out-and-out weird problems that many users will never experience for themselves. I’ve been following this traffic for six-plus-months now. I’ve seen credible reports of heart-wrenching, hair-pulling issues with Windows update, File Explorer, OS installation, and more. In digging into these issues and reported solutions, device drivers seem involved in at least half of them. As for the other half, “Windows registry oddities” account for many of those cases.
What does this mean? Windows 10 runs on 400 million-plus PCs, tablets, notebooks, and devices. Its long tail includes configurations with strange, peculiar, uncommon or outdated devices. I believe some unhappy and vocal users on this long tail are falling victim to gaps in a well-established and -oiled device support system . Indeed, it covers the vast majority, and covers it reasonably well. I’ve been mucking around with device drivers since the mid-to-late 1990s (about 20 years or so). Along the way, I’ve learned what hoops one must jump through, and the sources one must mine, to fix driver problems. I don’t think the same is true for many Windows 10 end users. What we’re seeing recently with complaints and decisions to roll back to Windows 7, 8, or 8.1 is this: that hardware works fine on older OSes, but not on Windows 10.
Taking the Sting Out of the Long Win10 Tail
Intractable driver problems are where barbs on the long Win10 tail start to sting. I’m not sure that it’s entirely Microsoft’s fault. Nor is it even the fault of the vendors who built the responsible devices and who typically write the drivers. It’s just that the whole distribution is big enough that certain parts of the long tail will have problems. And some of those problems will never be fixed. That’s because vendors don’t support Windows 10 on some device, or the driver has a bug when used with Windows 10 but not on older OSes.
Is this Microsoft’s fault? Probably not. But is it their cross to bear? Most assuredly! I’d urge them and the various communities that serve Windows 10 users to invest in more education to explain such things. They should also describe potential forms for relief. This is a rough patch on the PC landscape, but one that all need navigate. The long Win10 tail may never lose its barbs, but education may help them lose their sting.
Around the start of each month, I like to look at the numbers for Windows 10’s share of the desktop. This month, I’ll turn to NetMarketShare and analytics.usa.gov for my data. Their take on desktop share is depicted in the two following screen caps made December 2, 2016. Together, they help describe Windows 10 desktop share November 2016 end-of-month.
NetMarketShare shows Win7 finally starting to shrink, with Win10 at just under 50% of its portion of the pie.
Analytics.usa.gov shows Windows at 61% of Win7, and far fewer XP PCs active.
What’s New About Windows 10 Desktop Share November 2016?
I always like comparing these two sources of data. That’s because NetMarketShare (NMS) takes a more global look. OTOH, Usa.analytics.gov reflects (a lot) of visitors to US Government websites — 2.15 billion of them — over the past 90 days, for a more forward-looking and domestic American reflection of the relatively advanced population of users who visit them.
What do these numbers tell us? Windows 10’s overall share continues to grow, albeit more slowly than during the free upgrade period. Either source of data (or their average) shows that Windows 10 is closing in on the halfway mark for matching Windows 7’s massive share of the market (or has already passed it, as the 61% ratio of Win10 to Win7 on Usa.analytics.gov shows). The combined share of Windows 8 version currently stands at about 10% of the desktop space (or 5% of the total visitor space for Usa.analytics.gov, which includes both mobile and desktop OSes in its reporting).
What at least I find interesting — and I hope you do, too — is the disparity in XP share between the two sources. Windows XP registers at 2.01% of the desktop space for Usa.analytics.gov, but at 8.63% for NetMarketShare. I believe this shows quite correctly that first world users (in the USA, in particular) have pretty much entirely moved on from Windows XP, with just a few remaining diehard users. For the rest of the world, though, a relatively strong segment (almost one in ten users) is still running XP. I expect this divergence to continue, and perhaps to grow, as we track desktop share into 2017. The truly interesting question here is: how long can these diehards hang in there? We’ll just have to wait and see!
Late last month, I wrote a blog post about Windows Update (WU) Alternatives. Little did I know at the time that one of the tools I wrote about would so soon save my bacon. I’m talking about the Windows Update Minitool, aka WUMT. I learned this morning that WUMT does updates when WU can’t or won’t handle them. In this case, I’m talking about KB3201845 a Release Preview cumulative update to the Current Branch build.
First, I tried downloading that update through the usual means, and the download hung at 90% complete. Two more tries left me hanging, first at 45%, then at 0%. Realizing I was heading in entirely the wrong direction, I next downloaded the catalog element for KB3201845. I didn’t get it from the Microsoft Update Catalog (can’t find it there yet); I got links from TenForums.com (x86, x64). Because that cab file wasn’t self-installing, rather than find and use an installer, I turned to WUMT instead.
The ultimate outcome shows up as “Succeeded” in WUMT’s Update History.
[Click image for full-size display.]
How Is It that WUMT Does Updates When WU Can’t or Won’t?
Apparently, because WUMT accesses Windows Update servers independently, it can complete downloads and installations when WU is either blocked or misfiring. Though it took 3-4 minutes to download the ~937 MB that KB3201845 occupies on disk, it was able to complete that task on the first try. It also took some while to complete that installation, especially when factoring in the prep-before-reboot phase (5 minutes) and a longer-than-normal bootup sequence (5 minutes) that followed. But it did do the job, and nicely at that.
Assiduous Windows admins and power users will want to grab a copy of this free utility right away, which is available courtesy of the great guys at MajorGeeks.com. It’s already proved its worth in my toolbox. Why not let it do likewise in yours? If you need further inducement, it also works with Win7, 8, and 8.1 as well as 10.
Here’s an interesting tidbit from Dona Sarkar’s announcement for Windows 10 Build 14971 from the Windows Insider Program. Though it appeared on 11/17/16, I’ve been digesting this one for a while. Also, my experiments have produced thankfully positive results. The big news in that blog post is: Build 14971 drops Cmd.exe for PowerShell. The results of this change are best understood in showing output from Winkey-X for 14971 side-by-side with Current Branch.
Build 14971 on left, Current Branch on right, shows that PowerShell replaces Command Prompt.
[Click on image for full-size view]
Is There a Gotcha in Build 14971 Drops Cmd.exe for PowerShell?
After I’d said: “Yikes!” my immediate concerns produced two burning questions,
- Does this mean normal command line syntax won’t work anymore?
- Do batch files (ending in .bat or .cmd) run inside PowerShell?
Fortunately, recent experimentation shows that those questions’ answers are good ones. Thus, it’s a relief that normal command line syntax works fine in PowerShell. And for those with large existing collections of batch files, it’s probably equally comforting that batch files run just fine inside PowerShell. But there are some subtleties in running batch files inside PowerShell scripts. Some experimenting with multiple approaches usually produces necessary outcomes. But only bat file invocation and assignment of desirable variables are tricky. This StackOverflow exchange provides details: Safest way to run BAT file from PowerShell script.
Can’t Give Up Cmd.exe?
MS must be learning from past user reactions, because it also published workarounds to keep using cmd.exe instead of PowerShell. For one thing, cmd.exe still works. You can launch it through Cortana (the search box) or through Windowskey-R (the run box). Here’s a quote from Sarkar’s blog post on opting out of this change altogether:
For those who prefer to use Command Prompt, you can opt out of the WIN + X change by opening Settings > Personalization > Taskbar, and turning “Replace Command Prompt with Windows PowerShell in the menu when I right-click the Start button or press Windows key+X” to “Off”.
Maybe MS finally understands that not all Windows 10 users want or welcome every change. Personally, I think this change is a good one. But leaving the door open to old, tried-and-true tools and environments helps maintain good will with those admins and power users who feel differently.
Anybody who follows this blog knows I turn regularly to Sergey Tkachenko’s Winaero.com site for news and the occasional admin tool. I’ve been aware of his free (donationware, actually) Winaero Tweaker for some time, but never dug into it before. After seeing it come in for “honorable mention” repeatedly on TenForums.com lately, I decided to check it out. So far, I’ve found it as good at managing Windows settings and appearance as anything I’ve ever worked with. Its “Behavior” controls provide a good illustration.
Lots of nice tweaks here, for sure.
[Click on image for full-size view.]
Winaero Tweaker: Behavior Tweaks
These various items testify about what Winaero Tweaker is and can do. Its various Disable settings are particularly useful, and include:
- Automatic Maintenance (turns off the automatic maintenance task)
- Downloads Blocking (turns off blocking of file downloads in IE)
- Driver Updates (turns off driver downloads in WU)
- Reboot After Updates (turns off automatic reboot after updates, and wake to install updates)
These items address common complaints about default Windows 10 stuff, and make it easy to adjust the OS to less intrusive or disruptive behaviors. I also find the “Show BSOD, Disable Smiley,” USB Write Protection, and Windows Update Settings items helpful, too.
Winaero Tweaker also offers interesting boot and logon controls. These include easy access to boot options, lock screen behaviors, and login screen and behavior controls. They turn laborious Registry tweaks into one- or multi-click controls. You’ll also find nice network and user accounts controls as well, and various goodies here and there. I especially like the “Reset Icon Cache” item in the Tools section. It’s handy for fixing occasional icon cache corruption issues. In fact, the more you look around inside Winaero Tweaker, the more you’ll find to like about it. Highly recommended!
This will be the first in a multi-part series on free or low-cost tools worth adopting for Windows desktop admins. Here, we take a look at two free tools for Windows file management: WinDirStat and TreeSize Free. These are two widely used tools for inspecting and managing Windows files. Use them for a look at disk layout, or for finding large files (or folders) potentially for pruning. Both tools are highly regarded and frequently recommended at TenForums.com. I’ve used WinDirStat for over a decade myself, and am learning to appreciate TreeSize as well. Both make admirable elements in the Admin Toolbox: File Mgmt category.
Admin Toolbox: File Mgmt Item 1: WinDirStat
WinDirStat is a SourceForge project that has been around for a long time. It’s biggest strength is the “treemaps” it makes to depict how files lay out on a disk. These are based on the brilliant work of Dr. Ben Shneiderman, Distinguished University Professor in the Department of Computer Science at the University of Maryland, College Park, and the founding director of the University’s Human-Computer Interaction Lab. Here’s what WinDirStat shows me about the C: (Windows boot/system) drive on my production PC:
The big blocks provide immediate targets for investigation (and sometimes, cleanup).
[Click on image for full-size, more legible view.]
Here’s what’s hiding behind those big blocks by color:
Green (left, top): The biggest is my archive.pst file, which resides in my …\Documents\Outlook Files folder at 10.1 GB; its neighbor is my <ms-account-name>.pst file, which is now over 3.3 GB in size (that tells me its time to do some pruning there).
Red (center, top): The biggest is hiberfile.sys (the Windows hibernation file) at 12.8 GB; its neighbor is pagefile.sys (the Windows paging file) at a relatively svelte 4.7 GB given that my system has 32 GB of RAM.
Magenta (right, bottom): these turn out to be two Apple Device Software Update files (.ipsw) for iTunes at 2.3 and 1.7 GB, both in my Recycle Bin. Time to take out the trash!
The obvious appeal and utility of the visual layout of treemaps shines through clearly in this example. Ultimately, it helped me recover more than 7 GB of disk space (mostly from the .ipsw files in the Recycle bin).
Admin Toolbox: File Mgmt Item 2: TreeSize Free
TreeSize Free comes from German software company JAM Software GmbH. It presents users with a straightforward file hierarchy view of a target volume, with items listed in descending size. The tool is not as visual as WinDirStat. But it shows you where the bulk is. It also provides more insight into the sometimes mysterious System Volume Information folder found on every NTFS volume (shown on the following screen cap):
TreeSize isn’t terribly visual, but provides insight into the hidden contents of System Volume Information and more.
[Click on image for full-size view.]
Those who aren’t as visually inclined or who really want to dig into the gory details of Windows’ hidden files and folders will appreciate how TreeSize shows them what’s up under the OS’s hood. It’s equally good at helping users focus in on the biggest files and folders on a drive, albeit on a purely numerical basis from the file listings it provides.
Either of these tools will help admins or power users bring file systems under control. I myself prefer WinDirStat, but TreeSize can tell you some things that WinDirStat cannot. That makes both of them useful elements in the Admin Toolbox!
Advertisements are pretty unavoidable on your favorite websites and social media. Now users have to deal with them on Windows 10, too.
On its lock screen, Windows 10 displays ads for apps, games and movies users can download from the Windows Store. Windows 10 Home, Pro and Enterprise all come with the Windows Store — and its ads –built in.
“It’s something I’ve accepted, but that’s not to say I like it,” said Steven Powers, IT manager at Millar, a medical technology provider in Houston. “I hardly notice it now because I’ve become so accustomed to it. If I were a paying person, I’d be more upset over it.”
Millar deployed Windows 10 Pro as a free upgrade, and the IT department hasn’t heard any complaints from users about ads yet, Powers said. But users of Reddit’s forum for systems administrators have taken issue with Microsoft advertising to their enterprise users, calling it “unacceptable” and “insane.”
Some commenters complained that Microsoft posts ads despite businesses having already paid for Windows 10, but organizations that took advantage of the operating system’s free promotion period said it’s just the cost of using that complimentary offer.
Windows 10 runs on desktops and tablets, so it shows a lock screen on PCs similar to those on most smartphones and tablets, which is where the ads appear. The operating system displays suggested apps to download in the Start Menu as well.
There are ways to block the Windows 10 ads, however. In the Enterprise edition, administrators can turn off both the lock screen and Start Menu ads through Group Policy. In the Home and Pro editions, disabling the lock screen ads is a matter of turning off Windows Spotlight in the Settings tab. Users can turn off Start Menu ads in Home and Pro by switching off the Occasionally Show Suggestions option in the Start settings.
Another pop-up nuisance is when Windows 10 asks users for input on their experiences. If a Microsoft application adds a new feature, for example, Windows 10 randomly displays questions asking users what they think of it. Users can close the pop-up windows without responding, but it can be distracting when they’re focused on something else.
“That’s kind of annoying,” Powers said. “You might feel obligated to answer.”