Every now and then, I like to take a look at Windows 10’s so-called “Desktop Marketshare.” This means turning to a variety of sites that track such things. My go-to sites are NetMarketShare, Analytics.usa.gov, and Statcounter. In checking out Win10 desktop marketshare Nov17, I noticed some potent differences across these sources. Let’s look at some numbers, OK?
What’s Up with Win10 Desktop Marketshare Nov17?
Yesterday, November 6, I visited all three of those sites. There, I checked numbers for Windows 10, especially as compared to Windows 7. Here’s what I found, in brief tabular form:
|Comparing Win10 Marketshare, Nov17|
|Site||Windows 7||Windows 10|
I’ve heard plenty of folks call the Netmarketshare numbers into question. I read that they report only on sites that use their visit counting tools or belong to their site network. But I also notice that the numbers for Windows 7 are clustered much closer together (maximum difference 5.36%). By stark contrast, the Windows 10 numbers are more scattered (maximum difference 16.97%). Thus, I can’t help but take issue with Netmarketshare’s Windows 10 share estimate, for being too low with respect to the other two reporting sites.
I am indeed inclined to believe that around 4 of every 10 Windows desktops that access the Internet run Windows 10. This applies especially in the USA, as evidenced by the .gov site. (It’s most likely to attract its visits from within the USA.) But I’m curious to understand other components of the difference. Looks like Netmarketshare sees a lot more XP, Windows 8 and Windows 8.1 that the other two sites do. And for sure, plenty of die-hards do still run older Windows versions.
But, FWIW, I’ll put my credence into Statcounter and Analytics.usa.gov. Over the past couple of years their reporting has tracked my own personal observations more closely than NetMarketShare has. And what I see coming is visualized best at Statcounter, where the upward curve for Windows 10 and the downward curve for Windows 7 look likely to intersect very soon. If not this month (Nov17) then next month for sure (Dec17). Stay tuned!
If you’re running the latest Win10 version (Fall Creators Update Version 1709) and automate Update retrieval, you may be offered bogus printer drivers. Tools like the Microsoft Deployment Toolkit, aka MDT, or even the Windows Update MiniTool, aka WUMT, show Windows 10 images needing print drivers. At the same time, plain-vanilla Windows Update shows no such lack. That makes me label these items as bogus Win10 printer update alerts.
What Do Bogus Win10 Printer Update Alerts Look Like?
The following screen shot from WUMT appeared on one of my test machines this morning. I also observed those drivers failed to install. This TenForums thread applies: “Can’t get rid of Printer-6/21/2006 12:00:00 AM 10.0.15063.0 update.” That’s where I learned that what WUMT showed me also shows up in MDT for others. I expect that means it’ll show up in System Center Configuration Manager, the Windows ADK, SmartDeploy, ENGL Imaging Toolkit, and so forth. It seems to apply only to packages with automated Windows Update checks.
Closer investigation reveals the Print to PDF driver first, aand the XPS print driver second.
As it happens, neither of those print drivers is essential to proper print output anyway. The first one comes into play for the “Print to PDF option” in Office components and other applications. The second driver is an extension of the GDI-based Version 3 printer driver. It goes back to the pre-Vista Windows era (and is seldom used today). Thus, you can cheerfully ignore these offerings in most situations.
That’s why I elected to hide both drivers inside the WUMT interface. Because the program was happy to do just that, I won’t be bothered with this particular driver offer again. YMMV, depending on which deployment tool you’re using for Windows 10. According to one poster to the afore-cited TenForums thread, enabling continuation on error for updates in MDT allows deployment to proceed. It slows things down a bit, though, so consider yourself warned.
For some so-far undetermined reason, I’ll occasionally log into Windows 10 and find myself staring at a black desktop. Because I shoot LOTS of screen captures for articles, books, and whatnot, I usually set my background to all white. So when my background goes dark, I need a quick fix to turn the lights back on, so to speak. It turns out that fixing black Win10 desktop is pretty easy, if you use the Personalization tool. Simply right-click any unoccupied area of the desktop and you get a pop-up men that includes Personalize amidst its entries.
The option of interest shows up at the bottom of the menu.
How-to: Fixing Black Win10 Desktop
Once you click the Personalize entry on that menu, you’ll find yourself in Settings –> Personalization. Normally, when my desktop goes black, that means that Background remains set to Solid Color with a checkmark on the black box.
Getting back to white requires clicking Custom color, then moving the slider all the way to the right to turn black into white. That’s all there is to it for me. This is a big improvement over earlier Win10 versions (and Windows 8) which didn’t offer white as a custom color option. I actually had to capture a white field in a graphics editor, then save it as a file I could designate as my background. This is much easier and faster, too. Should you ever find yourself in this boat, now you know how to fix black Win10 desktop, too!
On October 23, just over a week ago I wrote that my 1709 upgrades to Windows 10 had gone mostly trouble-free. Alas, I was gilding the lily where one of my 1703 upgrades was concerned. At the time I wrote the post, the machine was in its final reboot phase just before handing off control to the new OS. That phase took about a week to complete successfully, as it turns out, and involved considerable research and what-if repair attempts to resolve. Everything I tried failed, until I discovered the cause almost by accident. As it turns out, bad RAM nixes 1709 upgrade completion. It also throws different errors on multiple failures, which makes diagnosis difficult.
When Bad RAM Nixes 1709 Upgrade, Then What?
On Monday, 10/30, I ran the hardware diagnostics from Lenovo Companion on the problem laptop. A Lenovo X220 Tablet, it has been (mostly) a rock-solid, trouble-free machine. The “Quick Random Pattern Test” for memory failed on that PC as soon as the test started. Reasoning that one of the SO-DIMMs might have failed, I popped the first one that came to hand (a Patriot 8 GB PC3-12800 module) and tried again. As luck would have it, the memory test went on to complete successfully using the sole remaining 8 GB module.
Alas, this is not what I saw from Lenovo Companion until after removing the failed/failing RAM module. I got the red X of failure instead.
Guessing that memory problems during the install could have caused my strange symptoms, I ran the Windows 10 Update Assistant one more time. And indeed, this time the OS installed successfully. My best guess is that the Windows Installer only attempted to access memory addresses above the 8192 GB high watermark for the first SO-DIMM during the final phase of installation. And it was only when the system tried to use the second SO-DIMM that things got wonky. Now that I’ve removed the apparently failing module, all is working properly on that PC. I’ve ordered a replacement from Newegg ($62.99 + $0.99 shipping) and will return to 16 GB operation as soon as it shows up at my front door. Case closed!
In the latest Creators Update Releases (Versions 1703 and 1709) when opening Internet Explorer (IE), the program opens a second tab to tout the Edge browser. It makes a not-so-subtle advertisement but also sets the focus on that tab. When I open IE, it’s because I want to use IE. So of course, I want to turn off IE Edge ad as soon as I see it. This turns out to require one simple Group Policy edit.
How-to: Turn Off IE Edge Ad
Indeed, there’s a Group Policy tweak that does this very thing. Fire up the Group Policy editor to make this tweak. I usually either type “Group Policy” into the Cortana search box, or simply go for gpedit.msc directly. Once you’re in the program, the navigation sequence is:
User Configuration -->Administrative Templates -->Windows Components -->Internet Explorer -->Internet Settings -->Advanced Settings -->Browsing
The Browsing setting is named “Hide the button (next to the New Tab button) that opens Microsoft Edge.” This must be set to “Enabled” to turn off the extra tab, as shown here:
A single setting targets and turns off the annoying Edge tab.
And What About the Newsfeed Page for New Tabs?
Yes, there’s a fix for that, too. It’s in IE Settings. Click the settings icon at Far right, then Internet Options, then click the Tabs button. In the Tabbed Browsing Settings window, find the “When a new tab is opened, open:” pick list. Select something other than the default “The new tab page with my news feed” to make an alternate selection. I usually go with “Your first home page” so I can jump right into Google search. You can do as you please here, as long as you pick one of the supported selections. For the record, this also includes “The new tab page” and “A blank page” as well. ‘Nuff said!
Note: Thanks to John Savill at Windows ITPro for the April 20, 2017 tip entitled “Remove Edge tab in Internet Explorer” that alerted me to the Group Policy tweak featured here.
For Build 17017 of the Insider Preview at least, and possibly for other recent Win10 builds or releases, a runtime error involving volsnap.sys may appear. These days, such errors are called “GSODs” because the screen that reports the problem is green. But I see reports of similar issues all the way back to Windows 7 days (when the error was called a BSOD, for “Blue Screen of Death”). Thanks to some nice detective work from Scot Hanselman, though, I knew just what to do when my Dell Venue Pro 11 hybrid PC fell prey to this problem. And as it turns out, Fixing Win10 Volsnap.sys issues is pretty simple, as long as you’ve got the right ingredients.
On the GSOD, an unhappy face emoticon sez the OS knows something ain’t right…
Ingredients for Fixing Win10 Volsnap.sys Issues
You need two things to address this problem. First, you need a known good working copy of volsnap.sys. I grabbed mine from one of my production PCs running the latest 1709 release. For the record, it lives in the %windir%\System32\Drivers folder. Second, you need a bootable Windows 10 installation or repair disk. I used the 1709 Windows 10 installer I built last week with the Microsoft Media Creation Tool (click “Download tool now” on the Download Windows 10 page).
Fixing Win10 Volsnap.sys Issues at the Command Line
The problem with replacing OS runtime files is that the OS that’s running, for all kinds of good reasons, won’t let you replace them while it’s running. You must instead boot to the install or repair media and make the replacement at the command line prompt therein. Because I used an MCT-based UFD, I booted to that drive, let the auto-start feature fire up the installer, then elected to repair an existing installation on the second screen in the sequence. From there, I took the Troubleshoot option, then opened the command prompt where I was quickly able to make the switch. To make my job as easy as possible (and following Scott’s suggestion from the afore-cited blog) I had already copied the known good working volsnap.sys to the root of the UFD from whence I’d just booted.
Here’s the sequence of commands I used to get myself going:
rem this opens the disk partition utility so you can identify installed disks
- list volumes
rem shows you the letters associated with disks on your PC
rem for this example C: is my OS disk, E: is the UFD I need to copy from
- cd <s>:\Windows\System32\Drivers
rem navigate to the proper directory for file replacement
rem <s> is the drive letter for your actual OS drive
- ren volsnap.sys volsnap.bak
rem keeps the old, broken version around under a different name
- copy e:\volsnap.sys volsnap.sys
rem copies the known good working copy into the proper directory
After you copy the good copy into the right directory, you can exit Command Prompt and restart your PC. When it resumes operations, any problems resulting from the damaged or buggy copy of volsnap.sys should be fixed. In my case, I immediately upgraded to Build 17025 on the affected PC. So far, no similar reports of volsnap.sys issues are reported for this more recent OS version.
It’s been 5 years now that Windows has included built-in support for mounting ISO files within the OS itself. Imagine my suprise, then, when I double-clicked on a Windows 10 ISO file and wound up inside 7-zip instead this morning. It seems that other programs can override default behavior, and take over the double-click role. That left me scratching my head, trying to remember how to mount an ISO using Windows Explorer. As with many such things, I found a Win10 ISO mount trick that works nicely. But first, I had to fumble through some trial-and-error to get it figured out.
On the vast majority of Windows 10 PCs, one need only right-click on an ISO file to provoke this pop-up menu:
On most Windows PCs, right click an ISO file, and the top entry says Mount, as shown here. Not on *this* PC, though. Sigh.
Playing the Win10 ISO Mount Trick
Here’s what I observed this morning on my problem PC. First, when I double-clicked the ISO file entry in Explorer, it opened in 7-Zip instead. Then, when I right-clicked the filename, the resulting pop-up menu did not feature Mount anywhere in its list of options. What to do?
It turns out that the answer is dead simple but a little counter-intuitive. If one selects the “Open with…” option (it appears in the foregoing list just below the first horizontal rule), a different menu opens. On the affected PC, that menu included 2 options: 7-Zip (first) and Windows Explorer (second). As it turns out, as soon as one selects Windows Explorer in that menu, the ISO is mounted as a virtual DVD drive. Admittedly, it’s not much of a trick, but it produces the sought-for result. To dismount the ISO, no such contortions are needed. The right-click “Eject” option works on all the various Win10 PCs I tried it on for testing purposes.
As with previous Windows Upgrades, the Fall Creators Update aka Build 1709, is coming in what Microsoft calls a “phased rollout approach.” In simple terms, this means if you leave the update to Microsoft, you’ll get it when they think it’s mature enough to install on your PC successfully. Of course, you can still force the update onto a PC at your discretion, through the “Download Windows 10” page. Thus, when it comes to rolling build 1709 out, there is no shortage of options.
This is what you’ll see on Win10 PCs after the upgrade completes successfully.
Have It Your Way When Rolling Build 1709 Out
Checking over the PCs here, I have 4 at my disposal eligible for the 1709 build. I normally have at least 6 such machines, but one got off track and has been running the Insider Preview version for a while. The other is my son’s Dell XPS 2720 All-in-One which is being retired, thanks to a recent spate of moderately costly component failures. (After replacing the screen and the power supply earlier, I decided not to keep fixing when the power switch quit working last month.) Three of those four machines have already been offered the update automatically:
- a 2012 vintage Lenovo T520 laptop (mobile dual core i7-2640M CPU, 16 GB RAM, 250GB Samsung mSATA SSD)
- a 2012 vintage mini-ITX PC (mobile quad core i7-3630QM CPU, 16 GB RAM, 250GB Samsung EVO840 SSD)
- the Surface Pro 3 (i7-4650T dual core, 8 GB RAM, 250 GB Samsung OEM mSATA SSD)
The only one that didn’t get the offer immediately from WU was my Lenovo X220 Tablet PC (same specs as the T520 in a smaller package, but no Quadro graphics). I find that curious because all of the hardware components that count are identical to those in the T520, though it has a touch screen and the T520 does not. That said, MS is clearly rolling out the upgrade faster this time than they did for 1703, for which the aforementioned mini-ITX PC didn’t get upgraded through WU as late as the end of August 2017 (it released in April).
Rolling Build 1709 Out Produces Acceptable Results
So far, all of those upgrades have eventually worked. I had to retry the Windows Upgrade Assistant on the X220 Tablet twice before it worked, proving that once again third time really is the charm. All the others got their updates from WU directly and experienced no obvious problems. I’m still in the post-upgrade cleanup process but so far everything seems pretty positive. I’ll keep reporting when and as things change.
If Microsoft’s usual release behavior holds true, Windows 10 Build 1709 appeared on Windows Update at 09:00AM PDT today. I just accessed WU from one of my f Current Branch PCs, and it came up immediately through Settings. Now that Win10 Build 1709 unleashed is on, what should businesses and the IT professionals who support them do? Good question!
For Fall Creators Update the download was available to nearly every PC I manage without delay.
Win10 Build 1709 Unleashed: Now What?
As mentioned in a previous post “Fall Creators Update Gets Simultaneous ADK,” the Windows Assessment and Deployment Kit for 1709 is also out today. IT pros can start kicking the tires on the new release right away. That’s smart, even if they don’t plan any production deployments for some time yet. I’d suggest visting one of the usual download sources and grabbing a copy. You could install (or upgrade) a test machine before the week is out. Then, you could dig into potential hardware and software compatibility issues (using the assessment tools from the ADK if you like). That’s when you’ll get a sense of how much work is likely to be involved in moving up to this latest version.
Those usual download sources include:
- The Download Windows 10 page, which offers access to the Media Creation Tool (MCT).
- The Visual Studio Subscriber downloads page (formerly known as MSDN Subscriber downloads).
- The Microsoft Volume Licensing Service Center
- Windows Update (accessible through any current running Windows installation)
If my experience is any guide, it takes about an hour to work through an upgrade installation on a machine with 60-odd third-party/follow-on applications installed. YMMV, depending of course on your Internet link speed and the capabilities of the PC onto which the upgrade gets installed. For myself, I’ve been through countless Insider Preview installs of the same (or a very similar) OS over the past three weeks. That’s how I can also observe that for most users this process will complete with no undue muss or fuss. Enjoy!
OK, everybody knows that the Fall Creators Update for Windows 10, aka Build 1709, goes live on 10/17. But on Friday, October 13, MS posted info about what else is available that day. This comes from the TechNet Windows for IT Pros blog, in a post entitled “Windows 10, version 1709 coming soon.” Key points for businesses and organizations mention availability via numerous online venues. These include the Volume Licensing Service Center, Windows Update for Business, Windows Server Update Services, and Visual Studio Subscriptions. Also, the Fall Creators Update gets simultaneous ADK (Windows Assessment and Deployment Kit) access. To the best of my knowledge that’s the first time MS has made the ADK available in tandem with a new OS release.
The 1709 ISO file to be released at the VSLC and through Visual Studio Subscriptions will include all major commercial Win10 versions. Enterprise and Education versions will be available sepearately.
When Fall Creators Update Gets Simultaneous ADK, What Does That Mean?
Windows 10 has been on a rapid update cadence since it made its debut in July 2015. It has delivered at least two major upgrades yearly since then. The life of a Windows 10 release is usually around 18 months. Indeed, the original build (1507) no longer gets updates as of November, 2017. That means organizations should access the ADK sooner rather than later, given a short life for any specific Windows 10 build. Even for companies on Current Branch for Business, pilot and testing efforts on Current Branch (1709 after October 17) must move quickly. That’s what makes this quiet announcement important for Microsoft. It’s also a form of “fair notice” to business and organizations to upgrade more quickly. Rather than the 2-3 year time lag typical for previous business migrations, they should track the 6-month gap between CBB and CB versions.
This represents a faster cadence for business adoption activities. Because these encompass pilot testing, software and hardware compatibility checks, deployment planning and staging, lots of work is involved. Hopefully, access to automated assessments for hardware and software compatibility will help. Ditto for automated deployment tools and capabilities. The ADK represents substantial time- and labor-savings for companies that dig in and put its tools to work. Presumably, faster access helps businesses squeeze a long-term process into a shorter overall timeframe. We’ll see…