Over the past two weeks, I’ve been engaged in a part-time exercise to rebuild my Surface Pro 3 from a clean re-install of Windows 8.1 Update 1. This has proved to be an interesting exercise for many different reasons, not least of which has been an ongoing trial-and-error effort to determine which of the latest device drivers that are currently available actually work on the platform, and which do not. I have come to the end of this particular trail, and now wish to report on my findings.
After one-at-a-time attempts to match all drivers to the DriverAgent analysis, I determine that 4 drivers must be “held back” to maintain stable, proper operation.
The other three drivers that do not appear in the preceding screen cap, in addition to the Intel HD 5000 graphics driver shown therein (running version 10.18.14.4029, but for which a newer 10.18.14.4156 version is available), are as follows:
Driver Name Working Latest Version
1. Realtek High Definition Audio 18.104.22.16898 22.214.171.12460
2. Realtek USB 3.0 Card Reader 6.3.9600.31207 6.3.9600.31208
3. Android Composite ADB 6.3.9600.17041 126.96.36.199
For each of these four drivers, installing the latest version causes the system to misbehave, by which I mean either an inability to shut down properly (usually because of the Pages_Locked_in_Memory error I reported on in earlier blog posts on this topic) or because the “updated” device fails to work properly or at all. Apparently there is some method to Microsoft’s madness in limiting drivers to those it has tested and vetted rather than the “latest and greatest” available, as programs like DriverAgent seek to identify and recommend. I just wish MS would keep a list of this stuff on its Surface Pro 3 pages so that finding out which ones work (and which ones don’t) could proceed from knowledge and insight, rather than the trial-and-error I had to conduct for myself (and which others in the same boat must presumably conduct for themselves as well).
I’ve just recently rebuilt my Surface Pro 3 installation, and am still recovering from that aftermath. Upon discovering a link to “Click-to-Run” installation for MS Office Professional 2013 on my refurbished desktop this morning, I decided to give it a try, and discovered a hidden benefit, or perhaps a cluster of related benefits. C2R, as I like to abbreviate Click-to-Run, is described as “a streaming and virtualization technology that is used to install Office products.” It works with Office 365 subscriptions (Office 365 ProPlus, Visio Pro for Office 365, Project Pro for Office 365, SharePoint Designer 2013, Lync 2013, and Lync 2013 Basic), but also with Office retail products (Office Professional 2013, Office Home and Business 2013, Office Home and Student 2013). Here’s what product information shows up about my brand-new install:
The C2R version of MS Office installs quickly and update automatically.
Imagine my surprise when the install process started and the runtime let me know I could start using Office apps right away, even before the install was complete. Sweet! Imagine my subsequent astonishment when I went to update the MS Office install (usually, this is a multi-step interaction with Windows Update that requires at least half an hour and sometimes as long as an hour to complete) and observed that the installation was already up-to-date. A little additional online research informed me that C2R retail installations, just like their subscription based counterparts, are updated automatically outside the Windows Update environment, and don’t require updates to flow through Windows Update at all. And for those who want or need to run multiple versions of Office side-by-side on the same PC, C2R for 2013 works alongside conventional installations of Office 2007 or 2010.
Good stuff! I’m going to try C2R on my next desktop build (or rebuild) and see how it works there, too. I’m curious to see what happens when, as is sometimes the case, I must run Office on a mobile PC when no Internet is available.
I’ve got two test machines upon which I’m running the latest Win10 build, namely 10049. In getting those machines up and running, I’ve found myself subject to 2 inadvertent gotchas along the way. Because one prevents the build from activating, and the other sucks up beaucoups disk space (about 2.5 GB) I’m going to share the fixes as well as explain what’s going on in each case.
Gotcha 1: All Language Packs Automatically Install
Through some no doubt accidental configuration setting, downloading Build 10049 from Windows Update automatically installs all available language packs for Windows 10. Although that current list includes “only” 19 languages at the moment, that still represents a lot of data which in turn sucks up substantial disk space. To uninstall unwanted language packs enter the command lpksetup /u at the Windows command line, then pick all the languages you wish to have uninstalled from the “Install or uninstall display languages” window that pops up in response. The whole process takes about 15 minutes to complete if you eliminate everything except your core language (and the base English MUI which is always installed). This also explains why installing Build 10049 seems to take longer to download and install than previous Win10 builds: it includes a whole lot more data!
It takes around a minute for each language to uninstall, so multiply that by 17 for total removal time.
Gotcha 2: Yet Another Hard-to-find Activation Key
If the ISOs are available for a Win10 build, all you generally need to do to grab the activation key for that build is to visit that page. But when the build is only in the “fast-ring” stage, the ISOs aren’t yet available, so one needs to do some hunting and pecking to find that key. This time around, I located an MS Community Wiki article entitled “How to activate the latest Windows 10 build” that provides the key despite also claiming that “By default, Windows 10 builds are pre-keyed, meaning, you do not have to enter a product key and should not be prompted to enter one even after Windows 10 has completed setup.” Alas, I must be either cursed or unlucky, because Windows Activation has demanded a key from me for every Win10 build I’ve installed from Windows Update so far (the ISO versions don’t seem to suffer from this gotcha, either). At any rate, you can find the key needed for a successful activation on that page if you need it, as I did.
“Why,” you may be thinking as you read the title of this blog post, “would I care about a high-speed interface on my desktop when it’s most likely to show up first and foremost on notebooks and tablets?” Why, indeed? And now that Asus has produced what looks like the first PCI-E x4 interface card for the Type-C version of USB, their promotional materials provide an interesting figure by way of a potential answer (but a potentially ticklish one, too, as I’ll explain further):
ASUS is apparently first-to-market with an adapter card to bring Type-C USB to older PCs with empty PCI-E x4 slots or better.
As you might expect, this great leap forward comes with at least one catch, and maybe two. Catch 1 is that you need to consume a PCI-E x4 slot to add just one USB 3.1 Type-C port to your PC. I’m going to guess that this may represent an expensive consumption of slot space for many users in the target audience for this hardware. Catch 2 is that exploiting the gains in read/write performance (which are for sequential data, and thus most applicable to laAnrge file reads or writes) requires support for something called “USB 3.1 Boost” that needs to be turned on in the PC’s BIOS to work. Right now, only updated ASUS motherboards using 9-series chipsets can take advantage of this feature. And finally, the only place I can find this item for sale right now is at SabrePC.com, where it goes for the princely sum of $95 (by way of comparison, I paid around $70 recently to add 4 USB ports on an x4 card that gave me four discrete ports, each with its own independent USB controller).
Right now, I’d put the USB 3.1 Type-C retrofit technology at the stage of “nice and interesting but by no means must-have.” I guess when it starts taking up significant mindshare with hardware and peripheral device makers and end-users alike, that stage will change. Here’s hoping!
[Note Added 4/7/2015: Found a link to a Sunix USB 3.1 card via Windows 10 Forums that proclaims itself to be “the world’s first USB 3.1 cards” available for delivery this month. The press release itself is undated, but it appeared on Windows 10 Forums on April 1.]
Gadzooks! Has it really been 32 months since Windows 8 was unleashed on the world? Indeed it has, and supplanted even, with Windows 8.1 in February of 2014. But only now are Windows 8 versions coming up to approach the fading majesty of Windows XP, as shown in this morning’s pie chart from NetMarketShare for Desktop Operating System Marketshare by version:
Windows 7 remains king of the hill, but at 14.07% Win8 versions are closing in on XP’s 16.94%
[Source: NetMarketShare 4/1/15]
I’m guessing we’ll see the numbers for Win8.* versions surpassing those for XP on or before the end of this quarter, at which point increasing interest in Windows 10 will probably put a quick cap on that current desktop OS’s overall growth. The “Vista effect” does indeed seem to be hampering Windows 8.1’s uptake, but hopefully this means that Windows 10 will enjoy an exaggerated bounce in adoption as a result.
While I’ve learned to live with Windows 8.1, thanks in no small part to Stardock’s excellent Start8 software add-on that brings the Win7-style Start menu back to Win8 versions, I’ve been learning to like Windows 10 quite a bit more since the technical previews started flying late last year. MS is doing a much better job of soliciting, listening to, and acting upon beta testers’ feedback with Windows 10, and it shows all over the place in the upcoming desktop OS. Although Stardock does have a Start Menu program for Win10, it’s not really necessary (I’m using it on one test machine to see how it works, but not on another, and am able to do everything I want on the OS easily without it). Applications and apps run seamlessly and even side-by-side in Windows 10, with no painful switches between the old-fashioned desktop UI and the new-fangled Windows Store UI needed or necessary (apps and OS UI elements run in windows on the desktop for those who base their operations in that mode). It will be very interesting to see when Win10 appears in the NetMarketShare pie chart, and how quickly that slice of the pie grows over time. Stay tuned!
In the wake of last week’s firmware updates for the Surface Pro 3, released outside the usual “Update/Patch Tuesday” timeframe, I decided to upgrade the drivers on that machine as well. I shouldn’t have: one of the RealTek drivers I updated (for either RealTek Audio or the unit’s built-in card reader, which handles the microSDXC card I used to extend storage) is apparently hooking pages it won’t release upon shut down. This provokes the “PROCESS_HAS_LOCKED_PAGES” error, and prevents the machine from shutting down properly (error code 0x00000076), and generally describes one of the symptoms of an ill-behaved or improper driver for the hardware it’s running on. Initially, I thought it was the Intel HD 5000 graphics driver, because discussion of the error message online pointed rather firmly in this direction. In fact, Action Center kept reporting an issue with the video driver, even though I had uninstalled the newer version and replaced it using the “Update driver” option on the device’s properties page in Device Manager.
When it’s good it’s very, very good, but when drivers go bad, it’s horrid!
“Fine,” I thought to myself, “I’ll just roll back to an earlier system image or restore point.” Sounds easy, but turns out to be harder than I expected it to be. The issue with a shut down problem quickly led me to understand that I couldn’t use a restore point from inside the OS (it still has to be able to shut down and restart properly for the restore point process to complete successfully, and thus also, deliver the desired outcome — namely a bootable functioning system with the older drivers in place). That’s why I found myself booting from a Windows 8.1 install UFD, and invoking the repair option after getting the installer up and running. Clicking through “Troubleshoot,” “Advanced Options,” and “System Restore” menu options, I was able to select an old enough restore point to precede the day my troubles started and believed I’d be able to resume operation with a known working set of drivers. But alas, Restore reported it was unable to access a file and was therefore unable to restore to the earlier state of things, observing that my anti-virus software might be causing the problem. Of course, this was an installer driven restore attempt, so there was no AV software in the picture. Very interesting!
As it happens, and much to my delight, Paul Thurrott released an article just yesterday (3/29/15) entitled “Tip: Be Prepared to Recover your Surface Pro 3 No Matter What Happens.” It describes where to find the files for a Surface Pro 3 (abbreviated SP3 from here on out for brevity) to creater what he calls an “uber recovery drive,” which requires a 16 GB flash drive (I dedicated a USB 3 Patriot TAB model I had laying around for this purpose). It also describes using the Windows 8.1 built-in “Create a recovery drive” to copy the contents of the recovery partition on the SP3 to a second and separate UFD, which need only be 8 GB in size as well.
Now realizing that I needed to rebuild the OS on the SP3, I decided to first try the factory refresh approach from inside the OS, after creating both of the UFD prescribed in Mr. Thurrott’s article. As I had feared, the results were that as soon as refresh sought to restart, the shut down error preventing the process from proceeding any further. The SP3 refused to start up from the uber recovery UFD, so I used Rufus and the Windows 8.1 with Update ISO to create an install UFD, and was able to get into the Reset Your PC mode where it stayed at 3% complete long enough for me to fear further difficulties. But then it advanced to 5%, 6%, onward and upward until the process completed successfully. Then, all I had to do was re-install all of my applications (which gives me a chance to check out Ninite, as I’ve wanted to for a while), after catching up on updates, to get back to where I started.
The moral of the story is: when it comes to the Surface models, stick to the drivers from Windows Update only. My urge to experiment really got the better of my caution and system savvy this time. I don’t intend to this again any time soon!
When I saw through the various news outlets that Microsoft had released an out-of-band Firmware update for the Surface Pro 3, I knew it was probably worth jumping onto sooner rather than later. Little did I realize that tinkering with device drivers might cause some heartburn along the way. Whereas other users who hadn’t updated drivers beyond the Microsoft recommended items reported little or no difficulty with applying the firmware update, I found myself unable to do so for some time. The issue stems from one of the “unauthorized” drivers causing an issue upon shut down (which necessarily precedes restart) that prevented the system from achieving a normal and complete shutdown.
This issue is important because the handoff from the OS to the low level boot routines must succeed prior to shutdown, so that the firmware files (which are run after UEFI/BIOS comes up, but before the OS itself boots) can be handed over and scheduled to be run during the next restart. And, without a proper shut down, I found myself unable to achieve the restart that included loading and installing those new firmware updates. Eventually I was able to solve my problem by selecting only the Firmware Update for installation, after which the whole process went through without a hitch, and now the system is running more or less as it should be.
Some filenames here are more helpful than others, but no version info or dates anywhere.
This led me to understand that one ventures beyond the recommended device drivers for the Surface Pro 3 at one’s peril, and also showed me that MS is not doing a stellar job of documenting what the correct set of drivers should be. Instead they provide a pointer to a download page for Surface Drivers, where one can find a list of driver files for download that might (or might not) be relevant to one’s actual driver needs. Searching on the KB numbers in those filenames, where available, helps shed light on some things (such as the type of device for which a driver is included) but no light on others (especially aggravating: no information about version numbers or dates of the drivers included).
Next week, when I have a little more time, I’m going try to rectify that deficiency with a little old-fashioned detective work. In the meantime, I’m replacing drivers one at a time until I can find the one that makes my BSOD upon shut down problem go away once and for all. If anybody has more insight into this issue than I do, or can suggest a better troubleshooting approach, please post a comment here and let me know what’s up. Thanks, and have a great weekend!
Last week, build 10041 for Windows 10 hit the fast ring for early adopters. Yesterday, it hit the slow ring for all adopters. I was able to upgrade my Windows 10 desktop without any issues during the fast ring phase, but I’ve been struggling to update my Dell Venue 11 Pro 7130 throughout this time period. The Windows Update driven version of the upgrade hangs part-way into the installation process and produces a vague and so far uninformative error message of “Update Install Failure, Error Code 0x800F0100″), both from the standpoint of telling me what’s gone awry, and from the standpoint of providing a fruitful point of departure for search engine research. I’m getting ready to reach out to contacts at Dell, in hopes that they might know more about this than I do.
When Windows Update doesn’t do the job, try the ISOs instead.
Here’s what I’ve learned so far:
1. The Windows 10 Build 10041 ISO’s are now available for download through Windows Insider. It was a total hoot grabbing 3.4GB in under 2 minutes, thanks to my newly-inaugurated high-speed connection, which averaged around 320 Mbps throughout the entire process.
2. I can’t find a working Synaptics touchpad driver for build 10041 through other channels (such as a Windows KB article) to try a manual update, and the Windows Update method keeps hanging the machine.
3. After several attempts with Rufus to build a working Windows install UFD, I finally put one together that allowed me to instigate an upgrade install for Build 10041 while running 9968 (I’ve added enough stuff to that machine that I didn’t want to have to reinstall everything).
4. What you can’t accomplish with an upgrade from Windows Update, you can overcome with an upgrade or clean install using the ISO files instead.
I’ve now successfully upgraded to build 10041, and update no longer calls for a Synaptics Touchpad driver update, so I assume I’ve gotten over this particular hump. It’s interest to troubleshoot when the guideposts along the way are few, far inbetween, and unfamiliar to boot. But so far, so good.
In reading about a new version of and model for web browsing in Windows 10, I often find myself nodding along and thinking “‘Bout time!” Over the past two years, I’ve been making a steady move away from IE to Chrome and Firefox, not necessarily because I want to, but because so many of the websites I visit either don’t work very well (or at all) in IE, and seem to work fine (or at least much better) in one or the other two of those browsers.
Can the once and future replacement for IE improve upon its recent foibles and failures? Here’s hoping…
Let me recite a few vexing cases in point:
1. Facebook: I’m nowhere near as active on Facebook as others I know, but I do drop in a couple of times a day to see what my friends are up to, and to post updates about blog posts, articles, and so forth. In IE, Facebook crashes or hangs pretty often (more than once a day) so I’ll often fire it up in IE, get stuck or hung up, and simply switch to Chrome instead.
2. LinkedIn: I use LinkedIn for a lot of different professional activities, and also post updates there, too, as on Facebook but also with curated pointers to quotes and articles. Lately, much of the active content on LinkedIn either doesn’t work, or takes forever to run, whereas it works quickly and easily on Chrome and/or Firefox. Same goes for Google+.
3. Hang one tab, hang the root executable: I used to think that browser tabs were pretty isolated from each other so that you could keep going with some even when one or more others encountered issues or slowdowns. Lately, I’ve found myself having to use Task Manager to identify which IE (tab) session is hanging or stuck, and hoping that a right-click to “End Task” will actually do the trick and bail out of the offending or failing browser tab. Sometimes it works, but more often it doesn’t and I have to kill everything to get IE working properly again.
Here’s hoping that “Spartan” (or whatever the new Windows browser takes as its official cognomen) will fix all of these problems and more. Because I do still have to use IE for some things — particularly when it comes to MS downloads and such from MSDN and other Microsoft pages — there’s currently no escape from the occasional glitches it seems to throw my way. Do my hopes for a better browser from MS make me an incurable optimist? Maybe so, but as long as I’m tied to Windows, I’m inclined to wish, hope and pray that new efforts and initiatives can produce better and more reliable results. We’ll see…
A Reuters story from the WinHEC conference in China has got the Windows press and blog environment abuzz enough that it’s being widely re-reported in most such outlets. In the story, Terry Meyerson, the chief exec for Microsoft’s OS unit announced that Microsoft will offer free upgrades to all Windows users, regardless of whether they’re upgrading from a legitimately licensed older copy of the OS, or something else (such as a pirated copy of the OS, for example). Meyerson is quoted as follows: “We are upgrading all qualified PCs, genuine and non-genuine, to Windows 10,” According to the story, Microsoft’s “plan is to ‘re-engage’ with the hundreds of millions of users of Windows in China.”
Given the high degree of piracy in China — Ars Technica quotes a BSA study that claims that “74 percent of commercial software in China is unlicensed” — this is actually a very clever move that will let MS find out who’s using their software and, hopefully, bring them into the fold of paying customers for add-ons such as Office 365 subscriptions, media subscriptions, and so forth. In addition, Ed Bott over at ZDNet followed up with MS and reported further that “…the plan to allow free upgrades for non-genuine copies of Windows applies to all markets and is not limited to China.” Bott even released this helpful upgrade matrix chart that shows how the upgrades will go, incidentally also revealing that Windows 7 users are eligible for the free upgrade as well.
Windows 7 and 8 versions will be eligible for the free Windows 10 upgrade, as shown. [Source: Neowin via ZDNet]
This is interesting news, and should be well-received globally, especially in those parts of the world where piracy is overlooked or tolerated. I think it’s a great way for MS to hook up with such users, and could redound to their benefit in the longer term. At any rate, it should be very interesting indeed to see how it all plays out and if it will ultimately pay off.