When you think of productivity suites, Microsoft Office most likely springs to mind. The applications in Office are some of the most ubiquitous in the enterprise, and for good reason. Office has tons of features and applications, and it’s relatively easy to use. This guide was even written and edited in Word.
But Office isn’t the only suite of productivity applications out there, and it’s not the right option for every company. Some businesses might want a more cloud-focused approach, in which case Office 365 or Google Apps might be the way to go. Companies looking for free access to word processing, spreadsheet and other applications can look to open-source alternatives such as OpenOffice and LibreOffice. Apple has its own suite for Mac users. And there are plenty of mobile productivity applications, some of which are free — even those from Microsoft, although they’re very limited without an Office 365 subscription.
It’s worth it to look at both desktop and mobile alternatives to Office, because the options are so competitive these days. Consider features, support, user needs and, of course, pricing. For many companies, Office could still be the best option. Volume licensing can help with cost concerns, and the continued updates and support Microsoft provides are a draw for businesses. Additionally, it’s important to think about the learning curve, help desk tickets and user frustration that can come from moving users to a completely new and potentially very different interface.
Still, taking another look at the productivity suite market can’t hurt. Begin with our new three-part guide, Alternative Productivity Suites Can Rock as Hard as Office.
Every now and then, one of my test machines will balk when the time comes to install a new update for testing and evaluation. Figuring that other readers may occasionally find themselves in the same circumstances, I wanted to share some potential fixes and techniques for dealing with this when and as it happens:
Windows Fixit: Automatically Reset Windows Update Components
Even though this Windows Support tool mentions only Windows 8.1, 8, and 7, it also works for Windows 10. It automates the process described in the afore-linked Fixit documentation, which includes stopping various services (BITS, Windows Update, and the Cryptographic service), deleting update queue management files, re-registering BITS and Windows Update files, resetting WinSock, restarting already mentioned services, and installing the most current Windows Update Agent. Nice explains why the Fixit is so handy, no?
This KB article (947821) explains how to use DISM (Deployment Image Servicing and Management) and the System File Checker at the command line to repair damaged Windows System files as a roundabout way to address Windows Update problems. Note that SFC /scannow currently returns spurious errors related to Nvidia drivers for current builds on the current branch (this is fixed in the current technical preview builds, however).
Research Specific Windows Update Problems Online
For my particular problem, I encountered error message 0x80070BC9. Searching on that error code online, I was able to find numerous helpful forum posts and information suggesting fixes. Most notably, posting to TenForums.com led me to a Microsoft Community post (February 2012) that mentioned that error code which contained much of the foregoing information. Direct research on specific symptoms are good, and error codes even better (if available) because they will often provide pointers to the most relevant and potentially useful information. A certain amount of spelunking and experimentation is usually required to adapt other people’s fixes to one’s own current situation, so be prepared to learn from such information as much from trial and error as anything else!
The Windows Update Fixit is a great place to start when seeking to remedy problems applying updates.
[Note: many thanks to Cluster Head at TenForums for pointing me in the right direction on this issue. It’s a great place to seek and find useful Windows troubleshooting information.]
With the introduction of a new Windows 10 Cumulative Update on a “once-a-month-or-better” frequency, it’s been said that clean installs should require only a few updates to bring a brand-new Windows 10 install completely up to date. After performing a bare-metal install yesterday on a new PC, I can confirm this is correct. After getting Windows 10 running on that machine, I visited Windows Update to see what was missing. I got a list of only 4 items, to wit:
- The latest Cumulative Update (KB3135173)
- A just-hatched security update to Adobe Flash (KB3135782)
- This month’s “Patch Tuesday” version of the Malicious software Removal Tool (KB890830)
- The current set of Windows Defender updates
That’s a list I would have to call minimal. It compares favorably to the dozens to hundreds of updates I’ve downloaded after performing clean installs of Windows Vista, 7, 8, and 8.1 over the past 9 years. (Vista went public on 1/30/2007, in case you can’t remember.) Cumulative Updates absolutely short-circuit the usual post install update drill, which often took an hour or longer on earlier Windows versions.
The new machine will replace my current production desktop PC. But first, I must transfer all of its hard drives over the weekend, and finish installing the usual work-oriented applications. Here are some other observations about my experience so far:
- Windows 10 did an ACE job of getting the drivers (mostly) right. According to DriverUpdate, it missed only 3 drivers on a configuration that included an Asrock Z170 Extreme 7+ motherboard, a Skylake i7-6700K CPU, 32 GB RAM, and the awesome Samsung 950 Pro NVMe SSD (512 GB). All were chipset specific items for system devices, all addressed by installing the latest Intel chipset driver.
- The process from bare metal to a fully-updated OS took less than 40 minutes. Some of that included idle time when the machine was waiting for input from me. It really is getting faster and easier to install Windows, and Windows 10 makes the process simple and straightforward.
- An NVMe SSD makes a BIG difference in system performance. Crystal DiskMark reported some startling performance figures. My results were consistent with Les Tokar’s discussion at The SSD Review in October, 2015. Here’s one snapshot of the performance data (his test machine configuration is nearly identical to my new rig: a deliberate purchase choice on my part):
The Samsung 950 Pro NVMe SSD is 3-6 times faster than the 840 EVO mSATA SSD in my current production PC.
Bottom line: the new regular cumulative update strategy for Windows 10 really does short-circuit most of the post-install catchup process for clean installs. Only those updates that appeared along with, or after, the most recent cumulative update will need to be applied, for any new Windows 10 installation. Bravo!
Sure, there’s a lot that’s new about Windows 10, and there have been a lot of changes introduced with the new OS. While some are positive, and some negative, nearly everyone has been unhappy about the lack of information on Windows Updates that MS has provided since Windows 10 went into full rotation in July 2015. Until yesterday, the most anyone could get out of MS about updates was boilerplate language along the lines of “Changes made to add stability…,”quality improvements, security fixes, and so forth.
Starting with the latest “Patch Tuesday” (2/9/16), MS has introduced a new Web page entitled “Windows 10 Update History,” that goes back to the old changelog approach of documenting new updates. Not coincidentally, yesterday’s updates also included a new Cumulative Update — namely, KB3135173. Here’s what that page has to say about it, as an illustration of the kind of information once again being made available:
This update includes quality improvements and security fixes. No new operating system features are being introduced this month. Key changes in this update include:
Improved installation time of updates.
Fixed issue with Microsoft Edge browser caching visited URLs while using InPrivate browsing.
Improved Silverlight performance.
Fixed issue that didn’t allow a Windows 10 PC to remotely configure a server.
Fixed issue with pictures and tables not displaying in Windows Journal.
Fixed security issues that could allow remote code execution when malware is run on a target system.
Fixed security issues in Microsoft Edge and Internet Explorer 11 that could allow code from a malicious website to be installed and run on a device.
Fixed additional issues with Input Method Editors (IMEs), Direct Access, assigned access, peripheral device detection, barcode scanning, Windows Explorer, Internet Explorer 11, Microsoft Edge, and scripting.
Fixed additional security issues with .NET Framework, PDF library, Windows Journal, kernel-mode drivers, Remote Desktop, and WebDAV.
For more info about the security fixes in this update and a complete list of affected files, see KB3135174.
For an audience that’s been half-frustrated, and half-appalled with the lack of information about Windows Updates for Windows 10 until now, this comes as very welcome relief. I must say I liked it better when you could simply click on entries in the Update History on a specific PC and get this kind of information, but the new approach is much, much better than the total lack of detail provided up until now. For the incurably curious, the information available within Update History remains pretty generic, though. Here’s the “detail” provided for the foregoing KB3135174 therein:
A security issue has been identified in a Microsoft software product that could affect your system. You can help protect your system by installing this update from Microsoft. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article. After you install this update, you may have to restart your system.
My best guess as to why MS has made this change, and introduced the Web page instead of returning to detail in Update History is that with multiple release branches now in place, it’s easier for them to manage all the data online. They don’t have to package that information for distribution with the updates any more, either.
As of the latest figures from NetMarketShare.com, Windows 10’s desktop operating system marketshare has just surpassed that for Windows XP, that venerable, creaky and insecure OS whose support went bye-bye when it hit end-of-life status on April 8, 2014. Almost two years later, it’s still kicking after a fashion, with various arms of governments world-wide (including branches of the US military) still paying for extended support contracts into 2016.
In fact, XP’s 11.42% marketshare still beats that for everything except Windows 7 (52.47%) and 10 (11.85%), including
- Windows 8.1: 10.4%
- Mac OS X 10.11 3.44%
- Windows 8: 2.68%
- Mac OS X 10.10: 2.33%
- Everything else: 5.4%
On the one hand, I’m amazed that XP has persisted as long as it has in “zombie status” (still in use after end-of-life has been reached). It’s a testament to various aspects of human organizational behavior, including inertia, parsimony, and sheer cussedness, none of which are especially flattering, but all of which are too apt to be denied.
On the other hand, it’s cool that Windows 10 has now jumped into second place overall. Now, it can start whittling away at Windows 7’s still unbeatable majority market share of 52.47%. Shawn Brink of TenForums.com observes that XP has been losing a fairly steady 0.5% in marketshare over the past year, which would indicate that it could vanish as soon as two years from now, or fade into the “other” category (less than 2.5%) in as little as eighteen months. We’ll see!
What I’m interested in watching going forward, is how well the dip in Windows 7 usage corresponds to the rise in Windows 10 usage. My guess is that Windows 10 will grow mostly by stealing from Windows 7 marketshare. I’ll keep an eye on this and report back in a few months.
NetMarketShare.com Desktop Operating System Market Share for 2/8/16 shows Windows 10 finally ahead of Windows XP. ‘Bout time!
There’s an interesting tool available in the Hardware Dev Center portion of MSDN: it’s called the Windows Imaging and Configuration Designer, aka Windows ICD. It’s designed to streamline the process of customizing and provisioning a Windows image. The home page for this tool states that it is designed to handle these tasks:
- View all of the configurable settings and policies for a Windows 10 image or provisioning package.
- Create Windows provisioning answer files.
- Add third-party drivers, apps, or other assets to an answer file.
- Create variants and specify the settings that apply to each variant.
- Build and flash a Windows image.
- Build a provisioning package.
Here’s the Table of Contents for digging further into this documentation (and the related tool). Note that you must first install the Windows ADK for Windows 10 before you can use this facility, and elect a specific set of options (all of which is covered in details in the “Getting Started” item below).
ICD uses a tile-based interface, and is both powerful and easy to use.
[Click image to see larger version]
|Getting started with Windows ICD||Read this topic to find out how to install and run the Windows ICD. Once you have Windows ICD running, check out the supported Windows ICD project workflows to learn about some of the things you can do using the tool.|
|Supported platforms for Windows ICD||Provides information about:
|Build and apply a provisioning package||You can use Windows ICD to create a provisioning package (.ppkg), which contains customizations that you can include for a particular Windows image. You can either apply the provisioning package to an image or share it as a standalone package that can be applied to a running system using the Provisioning Engine. For more information about PPKGs and how they are generated and applied, seeProvisioning packages.|
|Build a provisioning package with classic Windows applications||Create a provisioning package that includes Classic Windows applications and other files with your Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) devices. Uses:|
|Export a provisioning package||Export a provisioning package if you want to reuse the customizations already configured in a different project or to share it as a standalone package that can be applied to a running system during initial device setup or later.|
|Create a provisioning package with multivariant settings||Multivariant provides a generic mechanism for creating a single image that can work for multiple markets and reduce the number of images that OEMs need to create and test. It enables OEMs to dynamically configure language, branding, apps, and network settings during runtime based on the mobile operator and locale/country.
Windows 10 provisioning is an updated and enriched version of the runtime configuration or multivariant feature supported in Windows Phone 8.1. In Windows 10, multivariant is available for all Windows editions.
To provision multivariant settings, you must create a provisioning package with defined Conditions and Settings that are tied to these conditions. When you install this package on a Windows 10 device, the provisioning engine applies the matching condition settings at every event and triggers provisioning.
|Build and deploy an image for Windows 10 Desktop||You can use Windows ICD to create a new Windows 10 for desktop editions image and customize it by adding drivers, apps, language packs, settings, and more. You can also build the deployment media either to a folder or to a USB key.|
|Build and deploy an image for Windows 10 Mobile||You can use Windows ICD to create a new Windows 10 Mobile image and customize it by adding settings and some assets.|
|Build and deploy a Windows 10 IoT Core image||You can use Windows ICD to customize and create a new Windows 10 IoT Core (IoT Core) image.|
|Configure customizations using Windows ICD||You can use Windows ICD to configure the Windows device UI, connectivity settings, and user experience to better reflect your brand, to meet mobile network requirements, to comply with IT department security requirements, or to fit market segments or regions where the device will ship.|
|Use the Windows ICD command-line interface||You can use the Windows ICD command-line interface (CLI) to automate the building of provisioning packages and Windows 10 for desktop editions and Windows 10 Mobile or IoT Core images.
|Use the package splitter tool||Enterprise IT professionals who want to use a barcode to provision mobile devices during OOBE can use the package splitter tool, ppkgtobase64.exe, which is a command-line tool to split the provisioning package into smaller files.|
Just when I thought I’d seen just about everything Microsoft could do with Windows updates, the company pulled a fascinating rabbit out of its hat. I’m talking about KB3136562, a purportedly Cumulative Update to Windows 10 that bumps the build number from 10586.71 to 10586.79 but that shows up in Update History only as “Update for Windows (KB3136562). Here’s what’s interesting about this item:
- It is not yet available through normal Windows Update automatic download
- It requires manual download and installation, via the Windows Update Standalone Installer (x86 download/x64 download). This explains why those files end with the .msu file extension.
- There’s been no official word from MS about this update just yet, though numerous sources have provided coverage, including my personal fave TenForums.com and reddit.
- Most everyone who’s tried this update has reported successful installation, and it’s succeeded on 2 of the three systems I’ve tried it out on. It took some digging, but found the 0x80070BC9 error code for both failed install attempts on the affected machine.
At first, I believed that the affected machine’s use of the [en-GB] (British English) language pack, instead of [en-US] (American English) might have been at fault, but a question and reply sequence to fellow community members at TenForums disabused me of that notion. Now, I’m just scratching my head to figure out why it worked on most of my targeted PCs, but not on one of them. I’ll keep working it, of course, but such mysteries are what make working with Windows both extremely interesting and occasionally frustrating as well.
When the update installs, here’s the latest resulting WinVer output.
The big questions about KB3136562 can be stated as follows:
1. Why hasn’t MS released it through normal Windows Update channels?
2. Why is there no document page for KB3136562? (A search at Microsoft.com turns up zilch right now).
3. Why are the manual downloads available with no MS fanfare nor explanation?
If, like me, you’re incurably curious and just want to see what KB3136562 does, go ahead and use the download links provided in the bulleted list above. I’d suggest installing it only on a test machine, however, as it’s by no means a given that this update will ever be released through formal channels. Have fun!
I’ve been a big fan of Secunia’s (now part of Flexera) Personal Software Inspector (PSI) and Corporate Software Inspector (CSI) for half-a-dozen years or longer. The engine that makes both versions work scans PCs for installed software, and compares them to its sizable and comprehensive database of applications to see what’s up-to-date and what’s in need of patching or updating. But since the release of Windows 8, the software scanner engine has had a tendency to present an inert or perhaps comatose appearance to the OS long enough for it to register as unresponsive and to provoke errors that get picked up in the Windows Reliability Monitor on Windows 10.
That’s why I was glad to see the engine get an update in late January (to version 126.96.36.19904 for PSI, CSI uses the same agent on the PC clients it serves) that seems to have fixed this problem. I’m not sure what caused the lag between the software release and the OSes it serves, but it’s nice to have a good monitoring tool NOT act as a source of errors when it appears, to all intents and purposes, to be functioning properly and providing useful information and system guidance.
As far as scanning tools go, both PSI and CSI are worth checking out — and using, should your personal or corporate needs incline in their direction. This goes double, now that the latest release of the client-side engine (PSIA.exe) that works for both the personal and corporate versions of the software is no longer throwing potentially spurious “Stopped Working” errors on Windows 8.* and 10 PCs. At the UI level, the PSI scanner shows a (Not Responding) error while this situation works itself out in the background.
Note the APPCRASH error thrown by PSIA.exe on 1/2/2016: the latest release no longer does this.
Before the latest cumulative update for Windows 10 (KB3124262) appeared on 12/27, I’d already run into a problem with theKB3119142 “Update for Microsoft Visual C++ 2012 Update 4 Redistributable Package” on a couple of my PCs. I’d also fixed it fairly easily, having discovered numerous reports of this problem in various self-help repositories on the Web, most notably Answers.Microsoft.com and TenForums.com. As the repeated entries from the snippet of Update History from an affected machine shows below, the update keeps reinstalling and reinstalling though each installation is reported as “successfully installed.”
The fix, as it happens, is pretty straightforward, so I’ll provide step-by-step instructions:
- Open Control Panel
- Open Programs and Features
- Scroll down and right-click the entry that reads “Microsoft Visual C++ 2012 Redistributable (x64) – 11.0.61030
- Select “Repair” from the resulting pop-up menu
- Once the repair completes, reboot your PC if requested to do so
I haven’t yet found an explanation as to why this is happening, but it stops the endless cycle of repeated reinstallations cold. Given that 3 of my 7 current PCs experienced this issue, and that I see hundreds of reports from others suffering likewise, I have to believe this is a reasonably widespread phenomenon. Thus, I’m hopeful that an understanding that this problem, while vexing, is not terribly serious, along with a recipe to bring it to a screeching halt, will be helpful to those legions of Windows administrators out there. Given access to a decent automation facility such as PowerShell, AutoIt, WinAutomation, or something else in the same vein, one could easily script a quick utility to execute this repair on any and all affected machines during the next scheduled data cycle using your normal deployment tools.
The following screen capture makes it crystal clear as to the obvious symptoms that manifest when this issue is present on a Windows 10 PC (I count 10 recurrences in a 5-day period). If you start seeing something like this, now you know what to do!
Though successfully installed, KB3119142 keeps going like the Energizer Bunny.
On January 19, Microsoft released a System Firmware Update for the Surface Pro 3 that included an item related to Pen settings for the Surface Pro 4 Pen. In the wake of numerous subsequent reports of crashes and blue screens resulting from this item, MS has removed it from that firmware update (details appear under a “January 2016” heading on the Surface Pro 3 update history page). Alas, however, many people — including yours truly — had already updated their firmware with the original package that included the now-missing Surface Pro 4 Pen settings element.
Here’s how you can tell if your Surface Pro 3 is affected. In Device Manager, open the Human Interface Device entry, and check the version number for the driver associated with the Surface Pen Settings element. If your driver version is numbered 10.0.302.0, dated 10/22/2015, you’ve got the version associated with the Surface Pro 4 Pen installed; the most up-to-date version for the Surface Pro 3 Pen Settings is actually numbered 188.8.131.52, dated 3/20/2015.
The easiest fix for this potential gotcha is to simply click the “Roll Back Driver” button in the Surface Pen Settings Properties window on the Driver tab. This will automatically de-activate the 10.0.302.0 driver, and re-activate the 184.108.40.206 driver that preceded its installation. I followed a set of instructions from Liam Tung at ZDnet that had me uninstall the 10.0.302.0 driver, then restart the Surface Pro 3, which was supposed to automatically re-install the 220.127.116.11 driver by itself. Instead, I wound up with an Unknown Device in Device manager, which I was able to fix by pointing its Update Driver function at my local copy of the 18.104.22.168 driver already resident in my DriverStore folder.
I have to believe that the rollback fix is easier than digging into device designations (it took a while) to find the right one for the Surface Pen Settings item. But, all’s well that ends well, and now my Surface Pro 3 is humming happily along with no signs of crashes or blue screens in sight. Just another day in Windows-World, eh?
OK, now that’s more like it: proper driver now replaces improper SP4-only version.