Windows 10 – an Anniversary of Update Problems

Today’s BSOD of the day is APC_INDEX_MISMATCH.

I encountered this during a casual Windows update today. How annoying!

In particular, this update was the Windows 10 version 1607 feature update (aka build 14393), which corresponds to the Windows 10 Anniversary Update. This was the very first day of the update rollout here in Australia – 3rd August. The APC_INDEX_MISMATCH “stopcode” presented itself on each attempt of a Windows Update, where each time it failed with this BSOD and consequently rolled back. I tried various remedies from the internet: clean booting, removing the hyphen of the computer name, etc etc. (On one attempt, the stopcode even changed message to SYSTEM_SERVICE_EXCEPTION instead – who knows!?)

IMG_20160803_160944

A quick google search reveals that APC_INDEX_MISMATCH points to a driver issue. Various forums pinned the fault down to the Realtek HD audio driver, however these were old reports by users upgrading to Windows 10 from prior versions of Windows.

I find the Windows 10 Setup’s lack of error messages rather annoying, to say the least. Inspecting setuperr.log threw many red herrings! But I did know it had to do with a driver problem.

By pure trial & error, it turned out that my issue was caused an incompatibility with Symantec Workspace Virtualization. Maybe something in the Windows 10 kernel changed with this update?

Uninstalling Symantec Workspace Virtualization immediately remedied the situation on all affected machines. I may try see if I can still get this software to work at a later date (it is an awfully nifty product, which I had been using since it was owned by Altiris!), but for now it’s back to work.

Oh, and also, hi Bash!

(The Glasgow Haskell Compiler wouldn’t install, though)