Category Archives: Windows 10

Audacity Announces Data Harvest Plans

Dang! I just came across a news item that indicates one of my favorite audio recording and editing apps may be going over to the dark side. I’m talking about the long-time, well-known open source freeware program Audacity. Following  its April acquisition by the Muse Group, the program’s privacy policy updated on July 2. Alas, in that policy, Audacity announces data harvest plans. These include include telemetry data, and sharing of such data.

Audacity Announces Data Harvest Plans: What Kind?

What kind of data will Audacity collect? The types of data to be collected seem pretty innocuous. Namely, OS version, user country based on IP address, OS name and version, CPU. Also, non-fatal error codes and messages, and crash reports in Breakpad MiniDump format. I don’t see any personally identifiable information here, except for the IP address.

Who gets to see it? The desktop privacy notice reads “Data necessary for law enforcement, litigation and authorities’ requests (if any).” Legal grounds for sharing data are “Legitimate interest of WSM Group to defend its legal rights and interests.” That said, we also find language that reads such data may be shared with “…a potential buyer (and its agents and advisors) in connection with any proposed purchase, merger or acquisition of any part of our business…”

What has the user community most up in arms is that Muse asserts the right to occasionally share “…personal data with our main office in Russia…” This contravenes requirements of the GDPR, and could potentially violate data sovereignty requirements in certain EU countries (e.g. Germany) and elsewhere.

Does This Mean It’s Time to Bail on Audacity?

Not yet. These new provisions don’t take effect until the next upgrade to the program (version 3.0.3, one minor increment up from current 3.0.2) take effect. But a lot of people, including me, will be thinking long and hard about whether or not to upgrade. At a bare minimum, it might make sense to run Audacity in a VM through a VPN connection, to obscure its origin and user.

Note: Here’s a shout-out to Anmol Mehrotra at Neowin whose July 6 story “Audacity’s privacy policy update effective makes it a spyware” brought this chance of circumstances to my attention.

Note Added July 23: Audacity Updates Policy

If you check this story from Martin Brinkmann at Ghacks.net, you’ll see that Audacity has retreated from all of its controversial or questionable privacy policy language. Seems like the resulting user reactions caused them to revisit, reconsider and move away from data harvest that could touch on user ID info and addresses. Frankly, I’m glad to see this: I like the program, and am happy to understand its new owners have decided to leave its prior policy positions unchanged.

Facebooklinkedin
Facebooklinkedin

X1 Yoga Gen6 First Look

OK, I admit it. I’ve been sitting on this machine for a couple of weeks, buried in a mountain of other work. Ordinarily, I write my first look piece a day or two after a review unit shows up. Thus, my X1 Yoga Gen6 first look really includes a second and third look as well. And I must say, Lenovo has succeeded in injecting new oomph and vitality into a series of PCs that I’ve owned from them as far back as 2012. To be more specific, I’m talking about the latest iteration in the series: the ThinkPad X1 Yoga Gen 6.

Taking the X1 Yoga Gen6 First Look

Once I’d finished reviewing the ThinkPad X12 detachable tablet, I contacted the reviews team at Lenovo to request a loaner of this splendid little laptop. What they sent in response far exceeded my expectations. Here’s what this “Storm Grey” brushed aluminum laptop includes:

  • CPU: 11th Generation i7-1185G7 (4 cores/8 threads) 3.0 GHz
  • RAM: 16 GB LPDDR4X 4266 MHz RAM (soldered)
  • Graphics: Intel Xe Graphics Rev2
  • Storage: Hynix PCIe x4 NVMe SSD 512GB
  • Monitor: 3840×2400 Flex View Display (touch-enabled)
  • Ports: 2xThunderbolt 4 USB-C, 2xUSB-A 3.2 Gen 1, HDMI 2.0, Garaged Pen/Stylus, Headphone/mic mini-RCA jack, Kensington lock slot
  • Dimensions (HxWxD): 14.9mm x 313mm x 223mm x / 0.59″ x 12.32″ x 8.77″
  • Weight: Starts at 1.35kg (3 lbs: mine weighs 3 lbs 2 oz/1415g)

To my amazement, the current price for this unit as configured is ~US$3,800 (in round numbers, not including applicable sales or VAT taxes). This is a beast of a laptop, with an equally monstrous price.

What US$4K Buys You: Quite a Lot, Actually

The brushed aluminum deck and exterior are much more fingerprint resistant than my older X380 and X390 models in their standard Lenovo matte black finish. The construction is rigid and strong, with no real flex in either the keyboard or monitor decks of this 2-in-1 device. I found it easy and fun to use as a tablet with keyboard deck folded back behind. I found the keyboard just as usable and capable as most other modern Lenovo keyboards. For somebody who types for a living, that means a lot.

The speed of the RAM and NVMe SSD are pretty great, and the top-of-the-line i7 mobile CPU (1186G7) is likewise both powerful and capable. Right now, in fact, this laptop is the fastest PC at Chez Tittel and its 3840×2400 UHD panel the highest resolution display as well. In fact, I was amazed that the default scaling factor was 300%. That’s a good thing because I can’t see the text when it’s scaled 1:1 (100%). Touch is responsive, and the colors are vibrant and intense (500 nits, 90% DCI P3 color gamut).

The Thunderbolt ports come in really handy. In fact, they’re among the few Thunderbolt 4 capable input ports here at Chez Tittel. I’ve got several Thunderbolt 3 docks, which which the PC works splendidly, but so far I haven’t been able to stress test the high end of Thunderbolt/USB-C capabilities.

X1 Yoga Gen6 First Look.ssd-speeds

USB-C to the left with a Samsung 960 NVMe; Internal PCIe x4 Hynix NVMe to the right.
[Click image for full-sized view.]

So far, the internal NVMe CrystalDiskMark results (right-hand side of preceding graphic) are among the fastest I’ve seen here at Chez Tittel. The external NVMe is a Samsung 960 1 TB unit in a Sabrent USB-C SSD enclosure. Those results are also quite good. In fact, Macrium Reflect accomplished a complete C: image backup from the internal to the external drive in 2:46 with observed data rates of 1.7 to 2.0 GBps. On-disk size of the Macrium Reflect Image file (.mrimg) for that task is 22,821 KB (22.28 GB). That’s fast!

I Can See This Laptop as a Daily Driver

The target audience for this PC is business users. And in fact, I can see this device as a “daily driver.” If connected to  one or two external monitors, keyboard and mouse, plus extra storage through a Thunderbolt dock, I could use it as my everyday computing platform myself. The beauty of this approach is that one’s primary desktop turns into a traveling machine simply by disconnecting from the dock and heading out the door. I’d probably take my 1 TB USB-C attached external drive along, too for backup and recovery stuff on the road.

If you’re in the market for a high-end do-it-all machine, the X1 Yoga could be what you need. If you’re willing to plunk down the nearly US$4K it costs it can do the job. Then, if you’re willing to spend another US$1,500-2,000 to outfit it with additional accoutrement for in-office use it can serve as a primary computing platform. I’m thinking 2 27″ monitors (Dell UltraSharp 27 4K), decent keyboard and mouse (I like Microsoft’s offerings), and 2x5TB or larger external HDs attached via USB-C or USB A 3.1 or 3.2 would do it. And of course, this recently built PC meets all Windows 11 hardware requirements, so upgrading should be a breeze.

Highly recommended, for those who can afford it. My 2019 vintage X390 delivers about 75% of the performance for less than 35% of the price, though…

Check Your Prices, Dude!

After feedback from Lenovo arrived to the effect that “list prices aren’t best prices” — a sentiment I wholeheartedly endorse — I did some shopping around online and found a Full HD version with touchscreen (all other components the same) for US$2409.07. The lower resolution screen also extends battery life, so may be a better choice anyway. In fact, Newegg has the same configuration for a mere US$1,689 (FHD touchscreen but all else the same). Perhaps my concerns for price are overstated? You bet! Should I have shopped around a bit before posting this story? Too right! Somewhat abashed, I strongly recommend the FHD version of this laptop as a “killer deal.” Sigh.

Facebooklinkedin
Facebooklinkedin

Three-Quarters of PCs Sold Can’t Run Windows 11

Figure the number of PC sales based on Gartner’s Q1 projections against 2020, and total PC sales for 2021 could top 363 million. Take that into account along with data shown in the lead-graphic  from Statista. You’ll get an astonishing ratio: at least three-quarters of PCs sold can’t run Windows 11. To be absolutely clear, that means PCs sold between 2006 and 2021. Thus, I am assuming that PCs built in 2005 or earlier are unlikely to skew this estimate. And if they do, they will skew it away from Windows 11 anyway…

The breakdown is this: 3.62B billion PCs were sold between 2006 and 2017 (the last year CPUs too old to run Windows 11 were made). OTOH, 1.16B PCs were sold between 2018 through the end of 2021. To get that number, I’m generously allowing Gartner’s Q1’21 growth rate to persist all year. Do the resulting math, and just over 24 percent of PCs qualify for Windows 11, while nearly 76 percent of PCs don’t.

Hence: Three-Quarters of PCs Sold Can’t Run Windows 11

Microsoft currently claims 1.3 B active monthly users for Windows 10. I think that puts the size of the active global PC population lower than 4.8B units sold 2006-2021. I’m inclined to believe this means that the ratio could be more in Windows 11’s favor than my sales-based analysis indicates. Even so, it’s indisputable that three-quarters of PC’s sold since 2006 can’t run Windows 11. What’s in question is how many of the PCs sold from 2006 to 2014 or so remain in use.

I just gave my old Lenovo X220 Tablet (built in 2011 and purchased in 2012) away. That’s because it really didn’t run Windows 10 all that well any more (Insider Preview Dev Channel, that is). I cheerfully concede that for PCs in regular use, the ratio may be more like 50-50 when it comes to those that can, and can’t, run Windows 11. At my house, the actual ratio was 60-40 (can/can’t).

Still, that’s an evocative ratio. It indicates that many users must consider a hardware refresh plus an OS upgrade to get to Windows 11. I believe it applies across the board, too. And by that I mean among households and consumers, plus businesses and organizations at all scales.

This phenomenon should make watching PCs sales over the next year or two very interesting indeed. Microsoft will be watching, the OEMs will be watching, and I’ll be watching too. Stay tuned!

Facebooklinkedin
Facebooklinkedin

Experience Pack 120.2212.3920.0 Follies

As it turns out, I should’ve read the Microsoft announcement more carefully. The Windows Insider blog post that announced a new Experience Pack warned me that things would be different for Beta Channel and Release Preview PCs. It said: “For Windows Insiders in the Release Preview Channel, this will be an optional update for you.” I just didn’t pay sufficient attention. And that, dear readers, led me to some unnecessary but still effective Experience Pack 120.2212.3920.0 follies yesterday.

What Kind of Experience Pack 120.2212.3920.0 Follies?

The kind where I decided that because WU didn’t offer my Release Preview PC an obvious and immediate download, I would get it by other means. So, I turned to TenForums.com, where sure enough. I found a thread with a link to a reliable online source. Because this was a .CAB file, I then ran DISM /add-package … to get it installed. It worked!

Then I found out that the Release Preview mechanism differed from the Beta Channel one. Beta Channel (Surface Pro 3) got a direct offer from WU. Release Preview had a new item show up as an “Optional Update” — just as the afore-linked blog post said.

Sigh. One of these days, I’ll slow down and pay more attention. I swear. As Jerry Pournelle used to say in his Byte column from Chaos Manor “Real soon now.” Fortunately, there’s usually more than one path between Points A and B here in Windows-World. Yesterday, mine took me off the beaten track, and had me do manually what WU would have done for me automatically. Sigh again.

Experience Pack 120.2212.3920.0 Follies.info

I did get here eventually, but not via the most direct route.

One More Thing…

I used DISM to install the KB5004393 update on the Release Preview PC (Lenovo ThinkPad X380). Thus it doesn’t show up in WU Update History (unlike the screencap at the head of this story, which came from the Surface Pro 3). Indeed, I had to go into Programs and Features and use “View installed updates” to find it instead. When you do things manually, reporting changes, too. A word of warning, by way of factual observation.

Facebooklinkedin
Facebooklinkedin

WU Extends X390 21H1 Offer

This morning, I checked Windows Update on the 2019 vintage X390 Yoga (i7 Kaby Lake 8th Gen) as is my daily practice. Lo and Behold! There it *finally* was: WU extends X390 21H1 offer. I immediately downloaded and installed that update. What you see for this story’s lead-in graphic is the “Restart required” status that popped up less than 2 minutes later.

When WU Extends X390 21H1 Offer, I Take It!

After clicking said button, it took another 30 seconds or so to get to the actual restart. After reboot, it took less than 20 seconds to get to the start screen. I was able to RDP into the X390 with no delays to produce a 21H1 Winver screen (clipped to cut off email address).

No sooner is the offer extended, than it’s taken up. I’ve been waiting for this, in fact…

What I didn’t see after this update was additional updates to bring the 21H1 image up-to-date. That tells me WU is still keeping 2004-20H2-21H1 in pretty tight synchronization. In other words, I didn’t need specifically targeted 21H1 updates, because the necessary bits were already present. They’d been applied to 20H2 and stayed in effect across the  image transition into 21H1. Good stuff!

Just for grins, I ran DISM … /startcomponentcleanup on the 21H1 image. It took a while to get anywhere, and left two persistent, supposedly reclaimable packages behind. I’ve seen this before, and expected a re-run to leave them untouched. It did, and quickly, too.

Another One Bites the Dust

At this point I’ve only got one more machine that hasn’t been offered the 21H1 update yet. Should be interesting to see how much longer that takes. Stay tuned: I’ll let you know when that happens.

Facebooklinkedin
Facebooklinkedin

Jabbering Transceiver Error Rears Its Ugly Head

My first real networking job was as a Networking Consultant for Excelan in 1988. That company was purchased in 1989 by Novell, where I stayed quite happily until 1994. My initial training for the position included learning a hardware-based protocol analyzer (the LANalyzer, in fact). One of the things we learned in class was a coax-based 802.1 10 Mbps transceiver could crash an entire physical LAN. This device had a classy alias: “vampire tap.”  It was scre-clamped onto a thickwire coax cable to add one or more  network ports. Sometimes, its built-in circuitry would go bananas and overrun the network with bogus traffic. This problem, known as a jabbering transceiver error rears its ugly head recently. It happened  on  one of the Chez Tittel GbE switch domains.

When Jabbering Transceiver Error Rears Its Ugly Head, Divide and Conquer

Here’s a quote from the 2000 classic by Charles Spurgeon: Ethernet: The Definitive Guide

The quote comes courtesy of Google books, pg. 107.
(I still have a hardcopy on my bookshelf).

I’m pretty sure that NICs don’t have transceivers any more, so they aren’t really subject to such failures. But similar behavior — specifically, failure of a switch domain — is well-known to occur when hardware problems bedevil a LAN segment. For a while there, I was chasing random network failures in my office. They would kick all the machines off the switch, but would gradually let everybody back on.

It wasn’t until I quit using the built-in GbE port on my retiring X220 Tablet PC that the problems stopped. I was able to confirm the issue by plugging the RJ-45 cable back into that until and watching the circus start back up. If I switched to a USB dongle instead, the GbE domain attached to either or both switches in my office worked fine. One is a standalone NetGear 8-port GbE switch, the other an 8-port switch integrated into my Asus 802.11AX WAP/router.

Historical Note

Divide and conquer was the recommended troubleshooting method to identify a jabbering transceiver. One would subdivide the cable segment by interrupting it at a repeater, and terminating each sub-segment. Whichever segment stayed broken had the failing device. Repeat until the device can be identified, then replace it. I did this for TRW in Austin in 1988 on an actual service call there…

It wasn’t really until I started the trip down memory lane to my first-ever Ethernet networking class in 1987, and my trip to TRW,  that I understood what was happening. The built-in GbE interface was failing, and acting like a jabbering transceiver. I can’t exactly say “everything old is new again.” But I can say, an old lesson learned came in handy. And indeed, that is the way things sometimes go, shooting trouble here in Windows-World!

Facebooklinkedin
Facebooklinkedin

Pondering Free Windows Upgrades

The world is expecting information about a new major Windows release on June 24. I’ve been watching the byplay and discussion of what could be new, and what might be next. For me, one question is paramount. Will the next upgrade be free? Or, will users have to pay for that privilege? That’s what has me pondering free Windows upgrades, as the Microsoft event comes in a just a few more days.

History  Guides Me, In Pondering Free Windows Upgrades

Let me think back on my own personal Windows history. I remember most early upgrades to Windows were neither free (because they came on “official media”) nor terribly expensive (because MS wanted users to stay current). If I remember correctly, upgrades cost US$50 to $99 for Windows 3.0 and 3.1. Windows 95 upgrades listed for US$109.95, but deals were sometimes available. Ditto for Windows 98, which also offered a pre-order price of $94.99 for upgrades to those willing to spend less sooner and get the media later. Windows Vista is the last version that I remember Microsoft charging a fee to upgrade and it cost more: US$120 (Home), US$200 (Business) and US$220 (Ultimate).

Since then, upgrades to 7, 8, 8.1 and 10 have pretty much all been free to those with legit, valid Windows licenses for previous (and sometimes older) versions. To my way of thinking, this says that recent history argues that a “next upgrade” should be free for Windows 10 licensees. OTOH, there’s plenty of older history that argues directly to the contrary.

Time Will Tell … and Soon, I Hope!

With a major announcement coming up on Thursday, June 24, we may soon be finding out what any upgrade deal will be for Windows 10 licensees. Because I have 10 PCs here at Chez Tittel, I’m more than a little interested in (and apprehensive) about the upcoming upgrade policy. In the meantime, I’ve got my fingers crossed that recent history trumps ancient history now that physical media are seldom needed, and OS downloads represent the most common and widely used distribution channel for Windows install files.

Facebooklinkedin
Facebooklinkedin

Tom Petty Got Windows Wait Right

As the community of Windows Insiders, journalists, watchers and hangers-on collectively holds its breath for June 24, I’m thinking about an old Tom Petty song. The name of the song, of course, is the 1981 classic “The Waiting.” The lyric runs “The waiting is the hardest part.” And wow, how true is that as time marches toward Microsoft’s next generation Windows event on June 24. For me — and I imagine, many others — Tom Petty got Windows wait right.

Because Tom Petty Got Windows Wait Right, Hang In There!

Earlier this week, a leaked version of what purports to be the next Windows release appeared online. Since then, all the usual Windows news outlets are abuzz.  These include WinAero, Windows Latest, Windows Central, OnMSFT, Thurrott, and countless others. All are awash in exposition and analysis of “what’s in there.”

Visit one or more of the widely read third-party Windows sites to see what I mean. On every one, stories about the leaked version dominate their home pages.  Here’s a quick “count analysis” of what I see. In fact, most of them have devoted over half their line items to this topic. Some go as high as 90 percent.

When the Hardest Part Is Over, Then What?

I’m crossing my fingers that MS will indeed release an official next-gen version during or after the June 24 event. Because I’m an Insider MVP I’m not allowed to write about details regarding leaks and unofficial releases, hacks and other similar stuff. That probably explains why I’m a little frustrated that there’s so much activity already underway that I can’t dive into just yet.

In the meantime, I’ll keep humming Mr. Petty’s tune and watching the clock. There’s really not much else I can do right now — except, of course, to keep plugging away at all the real work I actually get paid for. Do stay tuned: as soon as I can, I’ll start covering this next big Windows thing, whatever it turns out to be.

Facebooklinkedin
Facebooklinkedin

Upcoming PowerShell Updates Arrive via WU

Here’s an interesting tidbit. Starting with Preview edition 7.2 preview 5 or newer, Windows Update will take over responsibility for updating PowerShell as new versions emerge. Used to be it would notify users an update was available, but they would have to visit GitHub to grab the .msi,  or use a package manager to install the new version. But now, certain upcoming PowerShell updates arrive via WU.

It’s not clear when this will click in for production versions, but the shift is already underway for preview versions. If you download and install PowerShell 7.2 preview 5 or 6, you’ll be queued up for this grand experiment. (Visit the Releases GitHub page to find them.)

Rolling Out Upcoming PowerShell Updates Arrive via WU

As is typical when introducing new features and capabilities. MS will start this process with Preview editions of PowerShell. You can read more about the rollout plan in the June 16 PowerShell blog “Preview udpating PowerShell 7.2 with Microsoft Update.” Some registry tweaking is required, but the blog post provides all necessary commands in scripts designed for easy cut’n’paste use.

This is a nice step forward for Windows-heads who, like me, are regular and interested PowerShell users. It’s one step closer to real OS integration now. The post doesn’t say when this treatment will include PS production versions, but I’m hoping it will be soon. Perhaps it will come along for the ride into “next generation” Windows 10? Stay tuned, and I’ll tell you when that news hits.

Facebooklinkedin
Facebooklinkedin

Forcibly Upgrading 20H2 PCs Many Ways

OK, I’ll admit it. I got tired of waiting. This weekend, I forcibly upgraded my 20H2 production desktop to 21H1. As it happens, when forcibly upgrading 20H2 PCs many ways to the new version are open. I took one of the easiest: installing the enablement package. Links for x32, x64 and ARM64 versions are available at TenForums, via KB5000736 self-installing update files.

Forcibly Upgrading 20H2 PCs Many Ways Requires Follow-up

Of course, it’s been a while since KB5000736 first appeared on May 18. After I got through that install — which took under 2 minutes on my SkyLake i7-6700 PC — I had additional updates to install:

  • KB4023057: Update for Windows 10 Update Service Components
  • KB5004476 Out-of-band MS Store fix for Xbox Game Pass games

These took MUCH longer to download and install than the enablement package for 21H1, much to my surprise. Not all updates, apparently, can happen as quickly or easily as its minimalist changes (which mostly involve flipping switches for stuff already in the 20H2 OS).

Other Ways to Forcibly Upgrade from 20H2 to 21H1

Though it may be the fastest way to get from 20H2 to 21H1, other methods are also available. The Microsoft Update Assistant and an in-place upgrade install from mounted 21H1 ISO (both available on the Download Windows 10 page) will do the trick as well. But not only do these methods take longer, they also leave Windows.old and related cruft behind. That’s why I use the enablement package whenever possible. If you run out of patience like I did, I suggest you take the same route to get to 21H1 yourself. Enjoy!

Facebooklinkedin
Facebooklinkedin