DPC is Windows shorthand for “deferred procedure call.” As explained at Resplendence.com (makers of the outstanding, free LatencyMon tool) the Windows thread dispatcher (aka “the scheduler”) handles prioritization of threads scheduled for execution on a given processor. Assume a high-priority thread works its way into the scheduling mix. Then, lower-priority calls for service get deferred and higher-priority threads run sooner. If that results in audio services delay, this can cause “stuttering” in sound output. And that, in fact, is what causes DPC Latency. (Literally, this term measures the amount of time it takes for a deferred procedure call to finally get a turn at the processor — and playback for audio.) That’s why learning that KB4505903 fixes DPC latency issue is good news, especially for those with affected PCs. Here’s a tweet from MS Engineer Pete Brown from Saturday, July 27:
Tweet Proclaims That KB4505903 Fixes DPC Latency Issue
As the preceding tweet capture shows, KB4505903 gets credit for fixing DPC latency spikes in Win10 1903. That’s good news for those with PCs suffering from audio latency issues. If this applies to PCs in your care, use LatencyMon to make before and after measurements. These should show visible (and audible) improvements in audio behavior. LatencyMon is a good tool for troubleshooting PC audio issues. It’s worth adding a copy to your admin toolbox for that reason. Who knows when another Windows 10 version or update may once again introduce audio delays, clicks, pops, or whathaveyou? I’ve dealt with such stuff personally since the Windows 8.x era, and repeatedly with various Win10 versions, too. Better safe than sorry!
For more information on symptoms of and resolution for this issue, see these various TenForums threads:
If you’re anything like me, you’ve got backups upon backups for your Windows 10 systems. Sometimes, it’s useful to identify Win10 backup version info — that is, which version and build the backup contains. As long as you can access the files within the backup set, this turns out to be absurdly easy. That information is readily available via File Explorer, as long as you can access the file in the backup named ntoskrnl.exe. By default this file resides in %windir%\System32. Thus, on my PC it’s in C:\Windows\System32.
How to Identify Win10 Backup Version
First mount the backup, or otherwise navigate in to the backup file set. Access the aforementioned file (namely C:\Windows\System32\ntoskrnl.exe, in my case). Right-click on that entry to produce its properties window, then click on the details tab. You should see something like this:
The Build number appears as the last pair of numbers in the “Product version” string.
Getting from Build Number to Version Info
Personally, I work with this stuff so much I immediately recognize that the build number 18362.239 corresponds to the Windows 10 May 2019 Update, aka 1903. For older build numbers, even I might need a refresher. That’s when the table at Microsoft’s Windows 10 Release Information web page comes in handy. As this table snippet shows, you can map from the build numbers to the version pretty easily.
Careful inspection of this table based on the left-hand side of the build number (e.g. 18362) points right to the version in the leftmost column.
[Click image for full-sized view.]
And presto! That’s all there is to it. Easy-peasey, right?
Just for grins, I’ve held one of the PCs here at Chez Tittel in abeyance. My wife’s mini-ITX PC is built around a Jetway QM77 mobo with a mobile quad core i7 3630. It’s also got 16 GB of DDR3 RAM, and a Samsung EVO 840 250 GB SSD (SATA3). I deliberately left it running 1809 to see how long it would take for WU to offer 1903. This morning, that 1908 MiniITX PC gets 1903 update offer, and now it’s installed. That took a while, didn’t it? Here’s what winver.exe now proudly displays on her desktop:
That took a while, didn’t it?
Why 1809 MiniITX PC Gets 1903 Update Offer Takes So Long?
Let’s do some calendar math. Using the handy-dandy Date Calculator at TimeandDate.com, I determined that it’s 64 days from May 21, 2019 through today. May 21 is the date from Microsoft’s Windows 10 release information page that indicates that’s when the OS version hit the Semi-Annual Channel. Thus, it took just over two months for this particular PC to attain the status of “ready to receive 1903.” This PC does have two USB-attached hard disks (one for backups, one for extended storage). Thus, I believe MS waited for the blocking problem with USB-attached storage cards and media to clear.
Alas though, we’ll never know for sure. MS isn’t transparent about the criteria it uses to queue up systems for feature upgrades nowadays. But given that this system is home to an Ivy Bridge CPU (which were current from Q3 2011 through 2013), this doesn’t represent new technology. Still, it’s been a rock-solid, trouble-free “surf’n’email” machine for “the Boss” for 7 years and longer. Because she really doesn’t care what version of Win10 she’s running — as long as things work to her satisfaction — I was able to conduct this little experiment in patience and fortitude.
How the Upgrade to 1903 Proceeded
It took a good while to download and apply the upgrade. My best guess is the total time involved was just under two hours. At the end of that road, it showed the most current 1903 build (18362.239). So far the machine is running without any obvious hitches. I’m sure if something goes sideways, the Boss will be calling for IT support — me — soon thereafter. And so it goes, here in Windows-World.
Part of my routine system maintenance on Win10 PC is to use the built-in Reliability Monitor. I’ll check my PCs anywhere from once a week to once a month, depending on issues and behavior. Good behavior warrants less frequency; and slowdowns, flakeouts, and blue screens warrant more. I endured a couple of days of slow, balky runtime hijinks from my old Lenovo T520. Then I decided to see what Reliability Monitor had to say. Alas, results showed the reliability index at rock bottom with app issues abounding. “Wow!” I thought to myself “this cries out for repair.” And indeed, an upgrade Win10 repair install saves mangled T520 PC from further mayhem. Here’s what I found when I checked that machine:
Uncontestably, the WORST Reliability Monitor report I’ve ever seen. OUCH!
[Click item for full-sized view.]
How Upgrade Win10 Repair Install Saves Mangled T520 PC
First a couple of hopefully helpful explanations. Point one: a Reliability Index of 1 is as low as the tool goes. I’ve never seen one that low before. Notice that the T520 sported that value for the last 5 days shown in the visual report graph. Point 2: investigation of the causes for the low index values included a large number of built-in Windows Store apps that not only “Stopped working” (as shown in the screenshot) but that also kept firing errors a dozen times a day or more. The day of the massive dip, it dropped from just over 7 points to rock bottom (1) with errors related to application failures, windows failures and miscellaneous failures of a wide variety. Not good, and not work keeping, either.
When Windows gets irretrievably weird, there’s a kind of magic repair that can often restore things to normalcy. By performing an upgrade install of the same version of Windows 10 already running on a PC, one replaces all the OS components and restores all OS-related settings to their defaults. This does, however, leave third-party applications and files alone. That’s why it’s sometimes called an “upgrade repair install” or even an “in-place upgrade” (see the excellent TenForums tutorial on this topic for a more complete description, and step-by-step instructions for performing same).
Making the Repair Install
After looking over the Reliability Monitor report shows above, I immediately made an image backup. Then I visited the Microsoft Download Windows 10 page. There, I used the “Download tool now” button to create fresh Win10 installation media on a USB stick. Here’s what File Explorer shows for the Details on the Setup.exe file I used to perform my in-place repair install/upgrade.
The Build info appears under both the File version and Product version fields — namely, 10.0.18362.1. That’s how I knew I had the right version to perform the repairs necessary for my 1903 installation on the T520. About half an hour later, my repairs were complete. And since then, all I’ve had show up is a few minor odds-n-ends. All are well-known, familiar, and mostly benign. And now, my Reliability Index is somewhere between 8 and 10, which is where it normally lives on this PC. Problem solved!
Repair install completed, Reliability Monitor settles back to normal. Whew!
If you ever find yourself in a similar boat, remember this kind of repair is good at fixing most Windows weirdnesses. It doesn’t take long to apply, and you should be able to tell relatively quickly if it helps — or not.
Yesterday (July 18), MS published financial results for the fourth quarter of its 2019 fiscal year. (MS FY runs from July 1 of the preceding year to June 30 of the current year.) Those results include a variety of interesting tidbits, many of which speak to the company’s future directions and its sources of success. In this connection, it’s also worth noting that MS continues on as one of only a handful of global companies with net worth in excess of $1TRN. With revenue of $33B, and net income and operating income at $12.4B, the kids in Redmond are clearly doing all right. Examined in a bit more detail, though, MS 19Q4 financials offer interesting insights to those willing to tease them out.
As of 7/19/19, MS total market cap stands at $1.06TRN.
[Source: Ycharts.com|Click image for full-sized view.]
Why say: MS 19Q4 Financials Offer Interesting Insights?
The subject nearest and dearest to this blog (and hopefully, its readers) is the Windows OS itself. Microsoft reports “healthy Windows 10 demand” in the Windows OEM Pro segment that resulted in 18% revenue growth. The company explained this also stems from the immanent approach of Windows 7 EOL on January 14, 2020 as well. On the other side of the Windows desktop OS street, however — the non-Pro (home user, end user, non-business user) segment of the PC market — MS reported an 8% drop in revenue. Its explanation: “continued pressure” in the entry-level computing category represents a falling tide that has dropped all prospects and activity. My own personal takeaway from this is a net positive: looks like business Windows users are finally coming aboard the Windows 10 bandwagon, and that we can expect a more orderly transition from 7 to 10 than many of us expected and feared.
Azure, of course, remains the king of the hill, and grew by 64% over the previous quarter. This produced $11.4B in revenue for the company (a 19% increase over the previous quarter). As Mehedi Hassan at Thurrott.com observed “Azure’s 64% growth this quarter is still the lowest in recent times, declining from the 73% growth it experienced in FYQ3.” These are the kind of growth rates that most orgs can only dream about or wish for. MS continues to grapple with them, quarter after quarter. No wonder Azure increasingly steers the overall direction and organization at MS!
What About Surface and Office?
Surface revenue is up by a relatively modest 14% for $1.3B total. MS cites ongoing, strong growth in the commercial segment. Given that it’s been a year or more since the launch of any new Surface devices, or significant refreshes to existing lines, that’s not at all bad. One hopes that Microsoft has more Surface tricks up its sleeve, though, and will deign to share them with the public before calendar year 2019 ends. Not much noise in the rumor mill to that effect, though.
Office also remains a strong and meaningful component in the MS product and business portfolio. The Commercial and cloud-based Office products are up by 14% overall, with Office 365 Commercial revenue up 31%. Office Commercial (boxed Office products) are down as more and more users switch to cloud-based subscriptions instead. On the Consumer side of Office, revenue is up a relatively modest 6%. Office 365 Consumer subscribers now number nearly 35 million. LinkedIn continues up with 25% revenue growth and Dynamics 365 likewise at 45%. Even search is up, at 9%.
Good News Brings More Good News
Given these cheery results, MS tells a positive story more or less across the board. According to YCharts, the company’s net market cap stands at $1.060TRN today.
[NOTE] There’s a fascinating write-up on MS from regular Economist business columnist “Bartleby” in the July 6-12th issue. It’s entitled “Send in the clouds” and is well-worth reading. It explains the profound and surprisingly well-managed culture change at the company that’s allowed it to switch its focus from selling software licenses to things like Windows and Office to a focus on cloud-based services and offerings built around Azure. Check it out!
After recent Windows Defender updates and the latest 1903 Windows 10 CU (KB4507453) Windows 10 may show interesting misbehavior. Symptom: running the sfc /scannow command produces error text rather than a clean bill of health. Reports from TenForums and Bleeping Computer confirm and describe this phenomenon. If you check the CBS.log file that the System File Checker produces, it identifies a Win10 Module named Windows-Defender-Management-Powershell as the culprit. The specific error says “Hashes for file member <filename> do not match.” In fact, what apparently causes recent Win10 updates bollix defender module hashes is proper resynchronization with the Component Store. I’ll depict the fix, then explain it further. [Note: this pathology is directly connected to Windows Defender, so Win10 PCs running some other AV/antimalware package aren’t affected. Interestingly, I did find the same error on current Insider Preview Builds, too.]
On both 1903 and 20H1 (18936.1000) systems, the symptom and the fix are the same, shown here.
[Click image for full-sized view.]
Fixing Win10 Updates Bollix Defender Module Hashes
The preceding PowerShell screen grab shows the symptom, and the multi-step fix. The symptom presents when sfc /scannow reports that “Windows Resource Protect found corrupt files but was unable to fix some of them.” Based on the nature of the actual error, this is a housekeeping problem. Microsoft’s installer clean-up apparently failed to synchronize hashes for those files as compared to the Component Store. Thus, the fix requires two steps, with a third to confirm a successful resolution:
- DISM /online /cleanup-image /restorehealth checks all the Windows files and replaces any it finds out of whack with known, good versions from the Component Store. This creates the situation where all copies of such files match.
- sfc /scannow, now able to work with matching sets of files, can now effect a proper repair because the hash values now match.
- A final iteration of sfc /scannowconfirms that all is well (“Windows Resource Protection did not find any integrity violations.”)
Problem solved. All this said, the fix may be something to entertain those with OCD tendencies rather than the general population. With issue reports abounding, MS should fix this issue soon. That means some upcoming Windows Defender update or Cumulative Update should obliterate this misbehavior. My money’s on a fix via Windows Defender updates, because this issue appears on Win 10 1903 PCs running Build 18362.239, Slow Ring Insider Preview PCs running 18362.1005, and Insider Preview PCs running Build 18936.1000. The only thing all those machines have in common is the same set of Windows Defender updates. Let’s hope it happens sooner, rather than later!
Note Added 1 Day Later (July 18)
This morning, I updated my Surface Pro 3 PC, running a recent Slow Ring Insider Preview (Build 18362.1005). The only new package that came through was Defender stuff (1.237.1331.0). Out of curiosity I next ran sfc /scannow. Sure enough, the same error message (and CBS.log file contents) recurred. Apparently, MS has not yet fixed this issue and the hash mismatch reappears upon obtaining new Defender updates. How hard can this be to fix? Please: get it together, MS!
A few minutes ago, I saw word at TenForums that a new slow ring Insider Preview release was out. Until now, this version has been more or less uniformly known as 19H2 (for 2019, Second Half of year). But as the following screencap shows, it appears therein as “Windows 10 Version Next.” That’s as good a name as any, I guess. But it is a change in nomenclature, which is why I say Windows 10 19H2 now called Version Next. Check it out!
Windows 10 Version Next may be the (or a) new name for the closer-in Insider Preview release formerly known as 19H2.
[Click image for full-sized view.]
Why is Windows 10 19H2 Now Called Version Next?
As usual, there’s a blog post for this new release. It appeared earlier today in the Windows Insider Program blog. It’s entitled Announcing Windows 10 Insider Preview Build 18362.10005 (19H2). What’s interesting about this post is that it continues to make reference to the release as 19H2. It doesn’t use the “Windows 10 Version Next” nomenclature either, in any way, shape or form. Kind of makes me wonder if whoever put the update package together didn’t use a bit of creative license in labeling same.
I guess we’ll find out if this is just a one-time use label, or a new name for 19H2 as and when other updates emerge. Until the next such item appears, we can’t be sure what’s really going on here. Right now, my best guess is that the Insider Preview Slow Ring version is still called 19H2. “Version Next” will either turn out to be a one-off synonym, or a new official name. Only time will tell!
[Note: Here’s a shout-out to Shawn Brink at TenForums, whose post New Windows 10 Insider Preview Slow Build 18362.10005 (19H2) – July 15 brought this release to my attention. Thanks!]
Hello again! I’ve been quiet for almost two weeks, off on vacation. When I got back to the office yesterday, I found a plethora of Win10 updates and upgrades pending. Right now, I’m running 9 PCs in my office, so resuming work underscores routine Windows admin workload for sure. The mix of OS versions looks like this:
- 2x 20H2 Insider Preview PCs (Dell XPS 2720 and Lenovo X220 Tablet)
- 1x 19H2 Insider Preview PCs (Surface Pro 3)
- 6x 1903/May 2019 Update PCs (3 homebrew desktops, Lenovo X380, Carbon Extreme and T520 laptops)
Upon my return to the grind, I had work to do on all those PCs to catch them up with the leading (and in some cases, bleeding) edge of Windows releases. Here’s a listing from David Xanatos’ outstanding Windows Update Manager that shows new updates for my production PC, for example:
New items show red boxes around July 11, 2019. MSRT shows a typical Patch Tuesday update.
[Click image for full-sized view.]
Why Say Resuming Work Underscores Routine Windows Admin Workload?
It’s easy to stay on top of Windows updates and upkeep on a day-in, day-out basis. But when you have to step away for a while, the level of time and effort involved in such work makes itself felt. So it was for me, who left the office on June 30 and didn’t get back into harness until the afternoon of June 11. A hiatus of 12 days doesn’t seem or sound like much, but it took me a good two hours to step around or remote into the stable of machines at the office and make sure everything was up-to-date and working properly. Indeed, it’s good to be back, but I didn’t really feel like I was fully present until I’d worked through catch-up on all those PCs. And so it goes for most of us, here in Windows World!
This is the first post from me for July 2019. My contract with TechTarget specifies 12 posts a month for this blog. With 12 days gone, and 11 posts to go, that means 3-4 posts a week from me for the rest of July. Consider this fair warning that after my absence and quiet, I’ll be something of a chatterbox (bot?) for the rest of the month!
A new Win10 WU (Windows Update) regime is now underway. Yesterday, I got my second CU notification from Windows Update, informing me that KB4501375 had arrived. Instead of downloading and installing on its own, I clicked the “Download and install now” hyperlink. This (see screencap below) fired off that process manually. What’s interesting is how I notice this change from the prior routine more at a visceral than an intellectual level. It is indeed a change, one that requires accommodating WU Download and Install Now behaviorally.
The CU routine has changed: 1. Look for “Additional updates available;” 2. Click “Download and install now” when ready
[Click image for full-sized view.]
What’s Involved in Accommodating WU Download and Install Now?
The preceding image caption gets right into accommodating WU Download and Install Now. It’s a two-step process that requires direct, manual interaction with Windows Update. Step 1 is to look at the update notification, with an eye for “Additional updates available.” When that text appears, it is necessary to click the (blue) hyperlink labeled “Download and install now.” When one does that, WU commences its download and install maneuvers for the related item (CU or Feature Update, as circumstances dictate). In most cases, installing a CU or Feature Update also involves (at least one) reboot for the target PC ( and multiple reboots for a Feature Update).
I’d thought this would be a totally routine and tolerable operation. But again, I’m surprised at how much my sense of routine, commonplace Win10 behavior is discommoded with this change. It’s going to take repeated exposure before it becomes “the new normal.” This time, however, it’s me that has to change to keep up with Windows. In the meantime, I have to remember to check for and follow the two-step process outlined above. I’ll get used to it, sooner or later. So will we all, I guess!
All’s well that ends well: WinVer shows me the .207 Build suffix after a successful CU update
I’ve been a huge fan of the French device driver site Station Drivers for a decade or longer now. Ever since it appeared on the scene in 2004, it’s been my go-to source for new, preview and hard-to-find device drivers. I don’t know where or how the site operator or his many minions and collaborators obtain some of the drivers they make available. It’s not unusual to find stuff on this site 2 or 3 months earlier than the companies that publish the drivers make them generally available. In particular, I’ve observed of late that Station Drivers provides latest Realtek UAD drivers both quickly and reliably.
When I read about a new 8701 version for the Realtek UAD driver at TenForums, I knew right away where to look for it.
[Click image for full-sized view.]
Station Drivers Provides Latest Realtek UAD Drivers, Pronto!
While perusing the threads in the Sound and Audio forum at TenForums yesterday, I came across mention of a new 8701.1 driver version for the UAD Realtek drivers. The link was to a CAB file, which takes some interesting contortions to access for drive update. “Hmmm,” thought I to myself, “I bet the same driver is up and ready for download on Station Drivers.” Sure enough it was, with a special silo for Asrock (to match the motherboard on the target system, a Z170 Extreme7+ model). This came in the form of a ZIP file that I unpacked into a folder on a working drive. Once I pointed DevMgr’s update function at that folder, it found and installed the new driver with neither muss nor fuss. Here’s that driver info:
The Real Test Comes from Using The New Driver
Lots of users have reported audio issues with 1903 — especially unpleasant playback latency or spurious clicks, pops, hisses and drop-outs. So far, I’m experiencing none of those things with my new driver install. Seems like the newest UAD driver works nicely on my particular system. But, as with many device related experiences on Windows 10, YMMV. Nevertheless, Driver Station remains a great resource for obtaining drivers for most Windows 10 devices. I urge you to try it out for yourself, the next time you’re seeking drivers for your Win10 PCs. It’s a nonpareil, for sure.