All posts by Ed Tittel

Full-time freelance writer, researcher and occasional expert witness, I specialize in Windows operating systems, information security, markup languages, and Web development tools and environments. I blog for numerous Websites, still write (or revise) the occasional book, and write lots of articles, white papers, tech briefs, and so forth.
Cool Tools, Insider stuff, Recent Activity, Updates, WED Blog

Database Mixup Prompts Bogus Update

Leave a comment

There’s always something interesting going on with WinGet, the MS package manager for installing and updating Windows stuff. Yesterday, a database mixup prompts bogus update orders for Visual Studio 2022. Let’s look at what happened, so I can explain the nit-picky little details involved.

But first: there really is no update involved. In fact, the Visual Studio version numbers are identical: 17.14.6, as you can see in the lead-in graphic. Note that the same version number appears in the columns for both “Version” and “Available.”

Fixing Database Mixup Prompts Bogus Update

The devil for these particular details lies in the difference between the two strings. The info from the “Version” column comes from the local copy of the WinGet source. It includes the parenthetical phrase after the version number — “(June 2025).” The “Available” version info does not include that string. Thus, there’s a mismatch, even though they’re the same base version number.

Simply put, because the version numbers don’t match, WinGet blithely assumes they’re different. Technically, they are. But they differ because somebody erred in creating one version string or the other.

Who’s on the Hook for a Fix?

Why Microsoft, of course, because Visual Studio is their product. Thus, they’re responsible for the package data in the WinGet database. As you can see in the following screenshot, in fact, that fix is already in. It depicts this morning’s WinGet show  and WinGet list data for Microsoft.VisualStudio.2022.Enterprise. Note that the version number info now agrees completely. Fixed!

The previous discrepancy is gone. [Click image to view full-sized.]

For further proof, I ran WinGet upgrade –all –include-unknown. It shows that CrystalDiskMark and Edge need updates, but Visual Studio no longer appears. The mismatch is corrected, so it’s no longer incorrectly flagged for update.

I’m a huge fan of WinGet, not least because the team at MS that works on its software and data is on top of things. Good stuff!

Facebooklinkedin
Facebooklinkedin
Device drivers, Recent Activity, Troubleshooting, WED Blog, Windows 11

Going Old School: X1 Extreme Driver Repair

1 Comment

In making my rounds this morning, I found the touchpad driver MIA on the Lenovo ThinkPad X1 Extreme (8th-Gen i7 CPU, c. 2018). On a machine of this august vintage, that could mean only one thing. Its driver must have gotten corrupted or gone sideways. That’s how I found myself going old school: X1 Extreme driver repair became my mission. Let me tell you what I did, and how I fixed that problem.

Going Old School: X1 Extreme Driver Repair Manuevers

No cursor from the touchpad meant some kind of driver issue, if not device failure. Hoping for the former, and dreading the latter, I started down the troubleshooting trail, as follows:

1. Reboot the PC. On a new boot-up and login, keyboard works fine but still no cursor.  Still no touchpad cursor, so I plug a wired mouse into the USB-A port to shoot more trouble.

2. Inside Device Manager, I find the touchpad driver as a Synaptics item under “Mice and other pointing devices.” I try reloading same via Driver > Update Driver > Browse my computer for drivers, then take what I’ve got from the “Let me pick from a list of available drivers…” branch. Reboot again: still no touchpad cursor.

3. Visit the Lenovo Driver Support page, grab the latest Synaptics Touchpad driver, and install same. Reboot PC again. Voila! Touchpad cursor appears and is working properly. Problem solved…

Final diagnosis: the on-disk touchpad driver had gotten corrupted. Downloading and installing a new one got the touchpad working again. Good-oh!

What’s (or Would Have Been) Next?

If the driver replacement hadn’t done the trick, my next move would have been to visit Settings > System > Recovery, there to hit the Reinstall now button to perform an in-place upgrade repair install. Note: this replaces all drivers as part and parcel of rebuilding the running OS image.

Had that failed, it’s pretty likely I would have had to decide if I wanted to fork over the money for a new touchpad and get it repaired, or attempt those repairs myself. I’m glad things didn’t go that far. Replacing a driver costs only time and effort, but no money. Touchpads aren’t free (Copilot says replacement cost is US$50-70, and if I had to take it to a shop that would add at least another US$100 or so). Again: glad no such repairs were needed. Case closed on a high note: it’s a good day in Windows-World.

Facebooklinkedin
Facebooklinkedin
Cool Tools, Insider stuff, Recent Activity, Thoughts & concerns, WED Blog, Windows 10, Windows 11

Strange Crystal Dew World Hiccup

Leave a comment

Yesterday, I noticed that both WinGet and PatchMyPC Home Updater hiccuped when trying to update CrystalDiskMark (8.0.6 to  9.0.0) and CrystalDiskInfo (9.6.3 to 9.7.0). This strange Crystal Dew World hiccup (that’s the home site for both apps) got me wondering if the developer had abandoned freeware versions of those tools for ad-driven (installer-based) or for-a-fee (MS Store) versions only. I’m please to report that my presumption was wrong, and new freeware versions for both programs are updating properly now.

What Caused This Strange Crystal Dew World Hiccup?

Apparently there was some delay between when the new version info got broadcast and when the Crystal Dew World website got updated. Indeed I saw web info (which serves as the lead-in graphic for the story) that led me to wonder if ad-driven (ZIP and Installer) or paid-for (Store) versions were the only remaining versions of CrystalDiskMark (CDM) and CrystalDiskInfo available.

This morning, however, when I went back to check again, things were different. I still see the same situation at Crystal Dew World (here’s a link to its CDM download which includes an installer named CrystalDiskMark9_0_0Ads.exe). But WinGet and PatchMyPC can both successfully upgrade these tools now (they threw “hash match fail” errors yesterday) and are proffering ad-free freeware versions that come from sourceforge (you can use WinGet Show CrystalDewWorld.CrystalDiskMark to reveal its database contents).

Updates Take Time to Propagate

I’ve seen similar things happen before — often, with MS facilities such as PowerShell and Windows Terminal — when an update emerges but packages and database contents don’t synch up. All in all, though, I’m glad that freeware, ad-free versions of these useful tools remain available. If they didn’t I’d have to find something else!

And, far too often, such things become necessary here in Windows-World. Not this time, apparently for CDM and CDI. Not yet, anyway… But the ad-oriented interface at Crystal Dew World strongly suggests it could happen if not now, perhaps later.

Facebooklinkedin
Facebooklinkedin
Cool Tools, Hardware Reviews, Insider stuff, Recent Activity, WED Blog, Windows 11

Interesting ThinkPad T14s Snapdragon Intake

Leave a comment

Here, interesting comes from the purported “Chinese” curse: “May you live in interesting times.” If fact, those times got a little too interesting for me once or twice last week, as I worked my way through intake on a the Snapdragon X version of the ThinkPad T14s from Lenovo (see “Speeds and Feeds” for more of those details). Indeed, I experienced what I choose to call an interesting ThinkPad T14s intake because of WU issues that popped up along the way.

Ultimately, I would have to send the PC back to Lenovo for a replacement because:

(a) I couldn’t repair a Windows Update error on the latest CU

(b) When I tried an in-place upgrade repair install, the PC asked for a BitLocker recovery key during one of the post-GUI install boot-ups. [The lead-in graphic shows this on its way to a fiery crash.]

I’ll admit it: I was caught unprepared. And when the Lenovo Recovery Media facility could only produce a USB key (no digital download for me, alas), an overnight swap was my only way to proceed. Sigh, sigh, and sigh again.

What Interesting ThinkPad T14s Snapdragon Intake Means

For me, it meant an irresolvable issue trying to catch the machine up to current CU levels. For the first time in recent memory the ElevenForum.com reset/reregister WU script failed to fix that, too. Thus I had to avail myself of the “Reinstall now” button in the options available from this Windows 11 24H2 instance via Settings > System > Recovery. That’s what you see as the lead-in graphic above, at 35% complete during the GUI install phase.

Along the way to catching the OS up, I installed a bunch of apps I like to use (12 in all: 7-Zip, Adv IP Scanner, CPU-Z, CrystalDiskMark, Everything, FileZilla, GadgetPack, Notepad++, PS 7.5.1, PowerToys, and Speccy). I also turned on Remote Access so I can view the desktop on a 27″ monitor instead of a 14″ laptop.

It was all good until I tried running WU. It was stuck, stuck, stuck, on the latest CU. It was throwing Error Code 0x800F0905, which Google tells me means “an issue with Windows Update or a corrupted installation file.” That’s why I went to the reset/register script immediately thereafter, and then Reinstall now when that failed as well. As I said earlier, I ended up swapping my ultimately bricked T14s for an identical replacement. It had to retry the stuck CU, but succeeded on a second attempt. So now I have a working T14s to play with for a while.

So following the well-known principle of “If you don’t get it right the first time, do it over,” I reinstalled all the apps I’d added to the first, bricked version. Then I enabled Remote Access so I can use RDP,  set up Windows Terminal and PowerShell, and I’m now fully off and running.

Speeds and Feeds, and More

The T14s Gen 6 model that Lenovo sent me includes the following:

  • Snapdragon X Elite X1E-78-100 CPU (3.4GHz, 12 cores/threads)
  • Adreno X1-85 GPU (built-in)
  • Hexagon NPU (delivers 45 TOPS)
  • 32 GB LPDDR5X-8448 MHz RAM
  • Samsung OEM PCIe Gen4 NVMe 1TB SSD
  • 14″ WUXGA (1920×1200, IPS, Anti-Glare, non-touch)
  • Windows Hello 1080P PHD camera, fingerprint reader
  • Qualcomm Wi-Fi 7 NCM825A 2×2 BE & Bluetooth 5.3
  • 2ea USB4 USB-C (40Gbps), USB 3.1 Gen 1 (5 Gbps) ports

As configured the unit currently goes for US$1,259 at the Lenovo Store. It’s sturdy, has a standard ThinkPad look and feel, and both thin and pretty lightweight (2.72lbs/1.24kg). It’s not quite as awe-inspiring as the less expensive Slim 7X model I reviewed almost a year ago, but it’s bigger, beefier, and pretty darn snappy. I will take it on the road with me at my next opportunity and see how it plays.

So far, though, it’s a solid performer and seems to get things done with verve. I look forward to a machine that will let me use the benefits of Copilot+ PCs in the near future. Indeed, that’s why I asked Lenovo to send me this unit. Stay tuned: I’ll tell you lots more, real soon.

 

 

 

Facebooklinkedin
Facebooklinkedin
Insider stuff, Recent Activity, Troubleshooting, WED Blog, Windows 11

Clearing Windows 11 ARM Spurious Reclaimables

Leave a comment

I’ve got a new laptop in from Lenovo. It’s a peachy-keen ThinkPad T14s (which I’ll describe in tomorrow’s post, so hold on for those deets). Today, what I care about is its Qualcomm Snapdragon X1-E78-100 CPU, which uses ARM64 not AMD64 architecture. This makes a difference, as I learned in clearing Windows 11 AM spurious reclaimables.

“What is a spurious reclaimable?” I hear you ask. It’s a Windows package in the component store (aka WinSxS) that sticks around, even after you run

DISM /Online /Cleanup-Image /StartComponentCleanup

to have it clean up reclaimable packages in said store. I blogged about this in March, when I explained how a single DISM /Remove-Package command could clear up two (2) spurious reclaimables seeingly built into Windows 11 24H2. This came courtesy of VIP expert @Bree at ElevenForum.com.

How-to: Clearing Windows 11 ARM Spurious Reclaimables

It turns out that those spurious packages for ARM64 are more or less the same as those for AMD64. But the names are slightly different for one of them. Unlike AMD64 a single /Remove-Package does NOT suffice to clear up both spurious reclaimables. Instead each package must be removed individually, as follows:

1. The initial syntax for each command line is the same: DISM /Remove-Package /Packagename:

2. The first package name replaces the “AMD64” with “ARM64” in its name with no further changes — namely Package_for_RollupFix~31bf3856ad364e35~arm64~~26100.1742.1.10

3. The second package name does the same substitution, but drops the minor version numbers from the end, too — namely Microsoft-Windows-FodMetadataServicing-Desktop-Metadata-Package~31bf3856ad364e35~arm64~~10.0.26100.1742

If you build up the entire command strings with the common stuff from item 1 above plus the bold text in item 2 (1st command) and item 3 (2nd command) you’ll clear out both spurious packages for Windows 11 24H2 ARM. Just a little bit different, but it does the trick.

Cheers!

 

Facebooklinkedin
Facebooklinkedin
Backup/Restore, Cool Tools, Insider stuff, Recent Activity, Troubleshooting, WED Blog, Windows 11

Learning New Backup Post-Blowup

2 Comments

I must confess. I blew up a Lenovo review unit Wednesday trying to fix an update problem. Now after what I learned during that experience, I’m learning new backup post-blowup. First, I’ll explain the need for new backup; then the blowup,; and finally, the backup and recovery manuevers I must now make part of my review process. It all ends with an ironic footnote, as my precautions prove unneeded.

To begin with, I’d like to thank Amanda Heater and Michael Redd of the Lenovo Reviews team, based in North Carolina. They didn’t even laugh at me when I told them what I’d done. They simply offered to cross-ship me a replacement system while I returned the one I so thoroughly munged. Thanks, thanks, thanks.

Why I’m Learning New Backup, Post-Blowup

It all goes back to Paramount Software, maker of the excellent backup and recovery toolset known as Macrium Reflect. I’ve been a happy and satisfied use of same for seven years or more. But as of January 1, 2024 (now 18 months ago), the company dropped its free version of that software. In good conscience that meant when I updated my ComputerWorld  story How to make a Windows 10 or 11 Backup, I had to recommend one or two free backup packages, as well as continuing my ongoing endorsement for Reflect (I own 8 licenses for version X and 4 for version 8, in fact).

So while I’m intaking the second iteration of a Lenovo ThinkPad T14s (the Snapdragon X variant of their thin-and-light 2-in-1 business laptop), I’m also learning how to install and use Easus ToDo Backup (one of the three free packages I mention in the February 2024 revision to the afore-cited CW story, the other two being AEOMEI Backupper Standard and MiniTool ShadowMaker Free).

It’s been both interesting and frustrating. I know Reflect so well now I don’t have to think about what I’m doing anymore: I just do it. In using Easus ToDo, I’m reminded of how idiosyncratic UI design can be, and how careful one must be in reading UI clues to understand how to define, schedule and run backups. Ditto for building and using recovery media. Long story short, I did figure things out, and I do have two backups of the T14s, working recovery media, and am ready to use them if needed. I’ve also saved a copy of the T14s BitLocker Recovery Key to a USB flash drive and my MSA.

What About That Blowup?

In working on the first of the two T14s laptops Lenovo sent me, I learned something about Windows 11 that I didn’t know, and would have preferred never to learn. In working through my normal intake process I ran Windows Update. It showed a pending CU that would not install, with the error code 0x8007000D, which indicates a corrupt Windows download or some issue with WU itself.

So naturally, I next ran the batch file from the Eleven Forum Tutorial: Reset Windows Update in Windows 11. This nearly always works to set WU back to rights, and let me get on with my updates. Not this time. The OS recommended, and my own experience concurred, that an in-place repair install was the next step in fixing this issue.

That’s where the blowup happened, as I encountered a Windows misbehavior I’ve never, ever seen before. I used the “Reinstall now” button in Settings > System > Recovery. It appears under the heading of “Fix problems using Windows Update.” It’s usually pretty foolproof and often turns a balky or misbehaving Windows OS into its tidy and proper counterpart. But first a short detour to describe the in-place repair upgrade or install.

More About the In-Place Repair Install

A repair install goes through two major phases. First, there’s a GUI-based portion, where it copies over the Windows OS installer and the files it needs to install the OS. Second, there’s a reboot after which a WinPE-based installer takes over and finishes building a new OS from a whole new set of files and data structures. Usually, Windows 11 reboots 2 or 3 times after the initial reboot as it finishes various aspects of that install process. When it’s done, a newly installed and presumably pristine version of Windows is running, usually devoid of the issues that prompted this repair fix.

This time, on either the first or second post-GUI reboot, the boot handler brought up a BitLocker recovery key screen. It also informed me that something about the boot environment had changed enough during the install that this key was needed to proceed. Ooops!

What Makes BitLocker Key Request a Blowup?

I didn’t have the BitLocker recovery key for that machine locally, and it hadn’t yet propagated into my Microsoft Account (MSA) online. I literally couldn’t access the hard drive. When I attempted to use the Lenovo image recovery service, I couldn’t get it to fork over a digital download. I could buy a pre-loaded USB for US$29 but it could take as long a week to make it to my door. Lenovo suggested that I return the unusable T14s to them, while they would cross-ship a new, working one to me for next-day delivery.

That’s the machine I’m working on right now. And my first steps on that second iteration were to:

  1. Install Easus ToDo Backup, and make a full-drive C: image backup
  2. Build the ToDo Recovery Media (this bootable flash drive will let me restore any ToDo image even if the C: drive is inaccessible)
  3. Make a file copy of the BitLocker recovery key to that same bootable flash drive, should I need for any reason. I also forced a copy into my MSA online as well (I don’t always travel with a full set of UFDs).

This is a new and permanent set of intake activities when I get a new PC or review unit from an OEM like Lenovo (I’ve also reviewed PCs and laptops from ASUS, Acer, MSI, Dell, Panasonic, and HP in past years). If a repair install can provoke the Bitlocker key request, I have to be ready for that. Now, thanks to the foregoing steps, I will be.

Ironic WU Conclusion

The CU that caused me problems on the first machine also needed installing on the second one. It was KB5063060 (26100.4351 Out-of-band). It failed on the first attempt right after the machine came up for the first time upon unboxing. But this time, the Retry button resulted in a successful installation. The machine’s all caught up and I didn’t need to run the in-place upgrade repair install, nor to recover from its failure (and supply the Bitlocker key on demand).

I was ready for things to go south. I’m grateful they did not. But, as I can attest from painful recent experience, it’s better to have the recovery tools and data and not need them, than it is to need them and not have them.

And wow, it seems ever so appropriate to recite this saga on a day emblematic of mala fortuna: please note that it’s Friday the 13th. It can be a risky day in Windows-World, as in other worlds as well.

Facebooklinkedin
Facebooklinkedin
Insider stuff, Recent Activity, Thoughts & concerns, WED Blog, Windows 11

Pondering US$200 4TB SSD Availability

2 Comments

I’m working my way up, slowly, to rebuilding a 5800X AMD desktop (on an Asrock B500 Extreme4 motherboard). The current build lacks a second M.2 NVMe SSD, so I’m also thinking about what kind (and how much) SSD to emplace in that currently open slot. Based on a teaser from NeoWin this morning, I’m also pondering US$200 4TB SSD availability, and its potential impact on that refurbishment.

Why Am I Pondering US$200 4TB SSD Availability?

Other than the obvious — amazing price for decent performance — I’ve got lots of reasons to think about choosing my second drive for this rebuild. Here’s a list:

  • I’ve got 3 or 4 good 1TB NVMe SSDs already in hand, all with 3K+ MBps read/write capability, plus 1 2 TB that’s PCIe Gen 4 and on par with the cheap-o 4TB item.
  • The B550 manual says the max capacity of SSDs it handles tops out at 2TB. So a 4TB unit might not even work.
  • I am trying to contain myself on this redo, price-wise, so I’m not sure I want to fork out another US$200, even though it’s a pretty potent price/performance combination.

Then I Started Thinking About HDDs

You can still buy a Seagate 5TB 2.5″ 5400 RPM hard disk for between US$140 and $160. That puts cost per TB on a roughly equal footing, though it does significantly impact performance. Indeed,  the HDD’s 450 MBps read/write is a decimal order of magnitude slower than this SSD’s reported 4,500 MBps or better. FWIW, I already own two of those so I could easily emplace one as a backup or archival drive in that build. Backup/archival space won’t be an issue, for sure.

So you see my situation: I have to think about what I want from the rebuild, and manage the expense versus capacity/capability ratio. I’ll keep thinking, and keep writing about it here. So far I’m leaning heavily toward “use what I’ve got, keep it cheap.” But that could change: Stay tuned!

Facebooklinkedin
Facebooklinkedin
Cool Tools, Hardware Reviews, Insider stuff, Recent Activity, WED Blog

Order EX5 Receive EX4 Request Refund

Leave a comment

Wow! I can’t believe what happened to me. I’m rebuilding the AMD 5800X PC in a new case, and ordered an Asus Thunderbolt EX5 to include, so I can try out Thunderbolt 5 and the Intel Thunderbolt Share application (licensed to a device or PC). Here’s what happened: order ex5, receive ex4, request refund (being processed), order again from Amazon. The replacement is on its way and should be here by Friday. All in all, I’m stunned.


As you can see from my carpet-based photo above, I received a ThunderboltEX 4, even though I ordered the next-gen version. Back it goes! Just printed a label and will send it back from the UPS Store later today. And to think I paid extra, because Amazon had none in stock that day. I should — and do — know better. Sigh.

Getting Past Order EX5 Receive EX4 Request Refund

All I can do now is wait. It won’t be terribly long, though because my Amazon Premium membership gets it delivered to me tomorrow, free. I need to try this item out so I can test-drive the Intel Thunderbolt Share application. It’s licensed to specific devices. And because I don’t have any laptops or docks with said license, this is a relatively affordable (~US$140) way for me to give it a whirl.

What I didn’t expect, after many, many years of entirely positive experiences with Newegg, was that one of their “stores” would try to slip me old wine and claim it was a new bottle. Not so, alas, and it won’t work for what I need it to do.

Ain’t that just way things go here in Windows-World sometimes? You ask for something specific for a supposedly included feature. Then you get something completely different, and deal with the aftermath. Sign again.

Facebooklinkedin
Facebooklinkedin
Cool Tools, Insider stuff, Recent Activity, Troubleshooting, WED Blog, Windows 11

X12 Gains QMR Support

Leave a comment

Wow! What a difference a day makes. Yesterday, Quick Machine Recovery didn’t work on my 2021 vintage Lenovo ThinkPad X12 Hybrid Tablet (with 11th-Gen i7-1180G7 CPU). This morning, the X12 gains QMR support and the test mode actually works. Methinks the edge of the gradual rollout just made it four generations back from the leading edge. (Copilot sez that if intel still used such numbers, Arrow Lake would like be 15th-Gen.)

If X12 Gains QMR Support, How Can You Tell?

Interestingly, even though the QMR test completes successfully on the X12, the QRM entry under Settings > System > Recovery — depicted from the 13th-Gen P3 Ultra ThinkStation above — is absent. Ditto for the QRM update (KB5056862) in Update History.

And yet, it works. Something isn’t precisely right around here, because QRM works (or says it completes the self-test successfully) without including those other presumptive signs of capability. It’s a bit confusing, if not at least mildly troubling.

Will the Circle Be Unbroken?

All this leaves me wondering how much further down the device chain this stuff will propagate. There’s a hard stop at 8th-Gen in that progression. Because my X380 is of that specific generation, all I can say right now is: “The update hasn’t gotten there yet.”

I just tried all the methods that the QRM article from MS Learn recommends to get it working when it opens to the WinRE boot screen, instead of going through its paces. Nothing doing, just yet. I’ll keep trying, and I’ll keep reporting: stay tuned and you can know, too.

Facebooklinkedin
Facebooklinkedin
Cool Tools, Insider stuff, Recent Activity, Troubleshooting, WED Blog, Windows 11

QMR Wants Newer PCs

Leave a comment

I have to laugh at myself. I’ve been waiting since Quick Machine Repair (QMR) emerged in April 2024 for it to show up on my Beta Channel test PC. (KB5056862 first appeared on June 2 for Build 26200.5622.) Alas, I probably could have kept waiting much longer. That’s because my Beta Channel test PC is built around an 8th-Gen i7-8650U CPU. But it seems that QMR wants newer PCs to include them in this gradual rollout. Let me explain.

Why say: QMR Wants Newer PCs?

I switched the Lenovo ThinkStation P3 Ultra, with its 13th-Gen i9-13900 CPU, over to Beta Channel. As soon as I brought up Build 26120.4230, WU extended the KB5056862 update. You can see that item in the Update History for that machine as the lead-in image above, in fact. What’s going on here?

It’s often the case that boot-related stuff on gradual rollout starts with newer PCs. It only makes its way back to older machines once MS is convinced that it really works as it should. And indeed, I followed the step-by-step instructions for testing QMR on the P3 Ultra (with the afore-depicted KB installed) from MS Learn’s Quick Machine Recovery article. It worked just like they said it would, too.

Meanwhile, the X380 Remains on Hold…

The older X380 is still on the outside, looking in, waiting for MS to extend the Quick Machine recovery update its way. I think it will keep waiting for some time yet. But at least, I have now been able to run the utility and see how it works. I’ll be reporting that in detail for an upcoming ComputerWorld story that’s due for submission on June 25. Stay tuned, and I’ll provide a link when that story goes live.

Facebooklinkedin
Facebooklinkedin