Tag Archives: featured

Insider stuff, Recent Activity, WED Blog, Windows 11, Windows Update

Build 22581 Hits Dev and Beta Channels

Leave a comment

Just yesterday, MS released a new Insider Preview build for Windows 11. That said, they changed that target audience up a bit. Whereas Beta and Release Preview channels had been paired, Build 22581 hits Dev and Beta channels. Out with the old pairing, and in with the new! I’m updating my beta test PC accordingly as I write this. But what does this mean?

If Build 22581 Hits Dev and Beta Channels, Now What?

For some info and possible insight, I turn to the 22581 Build Announcement. It makes the following observations about the change, ranging from channeling “Captain Obvious,” to a limited switcheroo, to ruminations on the roles that Dev and Beta channels play. Here are some illustrative quotes, under related headings.

Captain Obvious says:

Insiders in the Beta Channel can now try out new features such as Live Captions, Start folders, the redesigned Task Manager, tablet optimized taskbar and much more.

Switcheroo Info:

Now that the Dev and Beta Channels are receiving the same builds, the limited window has opened for Insiders to switch channels if you wish to do so by following these simple steps:

  1. Open Settings > Windows Update > Windows Insider Program.
  2. Select Choose your Insider settings.
  3. Select Beta Channel.
  4. The next time you receive an update, it will be for your new channel.

IMPORTANT: This window will close once we release builds with higher build numbers to the Dev Channel. If your device stays on the Dev Channel and receives a build that is a higher build number than what is in the Beta Channel, you will have to do a clean installation of the released version of Windows 11 on your device to switch to the Beta Channel.

See the announcement for more details, but I understand this as a promotion from Beta to Dev, with the opportunity to drop to Release Preview for those so inclined.

Channel Role Ruminations:

As a reminder, we are evolving the way we develop and release to Insiders with the Dev and Beta Channels now representing parallel development paths from our engineers. The Dev Channel will be a place where we will try out different concepts, incubate new ideas, and work on long lead items that may not get released to general customers. The Beta Channel will be the place we preview experiences that are closer to what we will ship to our general customers. However, this does not mean every feature we try out in the Beta Channel will ship. We encourage Insiders to read this blog post from last month that outlines the ways we’ll try things out with Insiders in the Dev and Beta Channels.

The Change Is Here, But…

I fired off my Beta test PC as I started writing this piece. When I just went to check status, the update had failed. A new error message appeared in WU “Save your work, and please try again.” Right now, I’m doing as directed and watching the update process. It sat at some while at 17% complete, but the count-up continues (and just jumped to 100%). Now it’s sitting at 100%. . . Another restart . . . spinning circle . . . Working on updates (with count-up) . . . and taking its sweet time (about 35 minutes total for post-GUI updates), it ultimately got back to the Windows 11 desktop.

AND NOW: my beta test PC is still running Build 22000.588. Here’s what WU has to say about the situation:

Obviously, further investigation is needed. Wonder what’s up? To that end, I’m using the Powershell cmdlet Get-WindowsUpdateLog to show me what happened. I’ve got some research work to do. But it may end up making sense simply to install the update using a mounted ISO to run setup.exe. I’ll report further tomorrow. Good fun!

Facebooklinkedin
Facebooklinkedin
Device drivers, Insider stuff, Recent Activity, Troubleshooting, Updates, Windows 10, Windows 11

GPU Driver Update Fixes Flickering Solitaire

Leave a comment

I cheerfully confess: I start most working days off with a rousing round of Microsoft Solitaire. When the game pane started flickering this morning, I asked myself “Time for a new Nvidia driver?” Sure enough, a new one issued on March 22 (yesterday). And, as usual, that GPU driver update fixes flickering Solitaire as desired.

Keep Calm and Carry On: GPU Driver Update Fixes Flickering Solitaire

I upgraded the Game Ready Driver to yesterday’s version 512.15 using GeForce Experience. The whole process took under 10 minutes. No reboot was required. Interestingly, Reliability Monitor collected no errors nor warnings while the monitor was flaking out on me, either.

It’s a good thing that the symptoms are both obvious, and easily diagnosed. And FWIW, a keyboard GPU restart (CTRL+WinKey+ Shift+B) didn’t fix things. That’s why I was hopeful that a driver update would make it all better. Luckily for me, that turned out well.

What If a New Driver Flops?

Things rapidly get more interesting if a new GPU driver fails to fix monitor flicker. First and foremost, I’d check cables next, starting (in this case) with the DisplayPort cables that stretch from the Gigabyte RTX 3070 Ti GPU adapter to the affected Dell 2717D. If a cable swap didn’t fix things, I’d try rolling back two driver versions or more (for Nvidia GPUs, that means using its manual driver search facility). If no joy after two or three older driver attempts, I’d next run monitor and GPU diagnostics.

Most of the time, it’s the driver. If it’s not the driver, it’s usually the cable. If I have to get down to diagnostics (usually available from GPU and monitor makers), things can quickly get expensive. Glad to have avoided such issues this time around.

But, here in Windows-World, it’s always something, right?

Facebooklinkedin
Facebooklinkedin
Insider stuff, Recent Activity, WED Blog, Windows 11, Windows OS Musings

Windows Ads Go Another Round?

Leave a comment

On March 15, The Verge published a story that raised a familiar Windows spectre.Responding to a tweet from fellow WIMVP Florian Beaubois (it serves as the preceding lead-in graphic), MS spokesperson Brandon LeBlanc is quoted as saying “This was an experimental banner that was not intended to be published externally and was turned off.” Indeed, it could be used in File Explorer to advertise the Microsoft Editor in future releases of Windows 11. If one ad is possible, others could easily follow. Is this cause for concern, or even ire? Whatever the case, it’s possible Windows ads go another round in upcoming versions.

If Windows Ads Go Another Round, So What?

There are several, hopefully worthwhile observations I can offer on the topic of Windows ads. Here they are:

  1. As the previously cited Verge story states, MS tried out ads in a 2017 File Explorer version. They were relatively easy to disable, and didn’t last very long.
  2. MS already uses ads on the Windows 10 lock screen, its Start menu, and in the taskbar. Once again, they can be disabled for those willing to search out related fixes.
  3. Other OS vendors — the Verge mentions Apple and Google specifically — also include ads on various products (e.g. iPhone, Apple TV and YouTube) that they bring to market.

Monetization Is Hard to Resist

What’s driving this phenomenon comes straight from what might be called “the capitalist imperative.” That is, seek out and exploit any and all opportunities to generate revenue. It’s what created Google, and what drives their biggest revenue streams. It’s what funds their search engine, and most other search engines besides.

I take comfort from knowing that there will be ways to turn off ads should they appear. If outright switches to disable them aren’t readily available, third parties will provide ad-blocker software to turn them off. I already use (and happily pay a voluntary “donationware” sum) for the “free” AdBlock Plus program to block web ads.

If I must, I’ll do likewise for Windows. I certainly hope it doesn’t come to that. But where there’s a will, there’s almost always a way to exert it as desired. Time will tell what happens with the ad capability recently shown to be possible in Windows 11. In the meantime, I’ll continue to enjoy that OS in its present (mostly) ad-free state.

Note [Added 1/2 Day Later]

Kudos to Sergey Tkachenko who published a story at WinAero this afternoon entitled How to Disable Ads in Windows 11. it provides a nice overview of all of the settings changes and registry tweaks needed to put them out of sight (and hopefully, out of mind) — if you’re so inclined. ‘Nuff said…

Facebooklinkedin
Facebooklinkedin
Insider stuff, Networking, Troubleshooting, WED Blog, Windows OS Musings

911 Works Even With Low/No Coverage

Leave a comment

In case you’ve wondered, I’ve been on a family vacation to points west. Our itinerary included great visits to White Sands (Las Cruces, NM), the Petrified Forest (Holbrook, AZ) and Tucson. While driving home on Friday, we found ourselves with a flat tire in a remote  area as night was falling. Our splendid E250 Bluetech is a great car, but does not sport a spare tire. Fortunately, I learned 911 works even with low/no coverage.

That’s extremely fortunate. Alas, I was unable to call out for local help. Mercedes roadside assistance needed to be dispatched from San Antonio, over two hours away from our then-present location. But dialing 911 on my iPhone 12, I was able to reach the local emergency response center.

Thank God: 911 Works Even With Low/No Coverage

At first, I was concerned that our situation didn’t count as a real “emergency.” Then my wife made several trenchant observations. We were nearly 20 miles from the nearest small town (the other, next closest was nearly 30 miles away). Night was falling. We were stuck on a narrow shoulder. Cars were zooming by, and our downhill stretch was a popular spot for faster vehicles to pass slower-moving ones. OK then: it was a bad spot to be in.

Her opinion: lack of local services, a bad location, and no outgoing cell or data connections meant it WAS an emergency. In less than a minute I was talking to a very friendly and helpful 911 operator. He agreed we needed help, and dispatched a tow truck from Brady, TX (about 40 miles away from our location).

Call Me Back, If You Hear Nothing…

Because the local signal was so weak, he asked me to call him back in an hour. When I did so, he said he’d tried to call me himself but couldn’t get through. A car carrier was on the way, and should be arriving in another half hour or so. Indeed, I’m glad 911 works to carry outgoing messages when other cellular traffic is impossible. Here’s an interesting explanation of what’s involved: How Can Mobile Phones Make ‘Emergency Calls’ When There’s No Network Coverage?

And indeed, about 90 minutes after my initial call to 911, a car carrier (my favorite brand: Jerr-Dan) appeared on the scene. Shameless plug: Henry, the helpful and skilled operator from Brady-based Back on Your Feet Towing had us loaded and back on the road in under 15 minutes. We would wind up negotiating a price to take our car to a tire repair center near our Round Rock home, over 200 miles away. It was infinitely preferable to spending the night in Brady, and waiting for repairs the next morning. As the ensuing repairs would prove, that was the right decision…

The Morning After

We wound up getting home after 1 AM that morning. Our flat occurred just before 8PM, with about 2.5 hours of driving time left to get home, But with several stops to refuel Henry’s truck, to check the tie-downs on our wounded car, and for bio-breaks, it ended up taking 3.5 hours to make the rest of the trek home.

At the tire repair place the next morning, I learned that the tread and the sidewall had started to separate on the passenger side front tire. I also figured out they were just over their 50,000 mile lifetime warranties. A new tire was immediately installed, and I’ll be ordering a new set this week. I have to imagine that in Brady we’d have waited hours for a replacement tire to come from Austin or San Antonio. In Round Rock, the whole repair took under half an hour!

We’re very lucky the tire didn’t fail more catastrophically. We’re also lucky that 911 works even with low/no coverage, even in the Texas boonies. That was an adventure I’d not wish to repeat any time soon.

Needless to say, we’re very, very glad to be home, safe and sound. A typical sentiment at any vacation’s conclusion, but more heartfelt than usual this time. And remember, when all else is unavailable, 911 is worth a try. Thank goodness it worked for us on Friday!

Note Added 1 Day Later: Worth Reading (and Remembering)

By default, the iPhone turns off Data Roaming (which lets a cellphone access other providers’ networks). Settings → Cellular Data → Cellular Data Options → Turn Data Roaming on. Had I done that on the deserted roadside, I’d have been able to tap into the same AT&T network my tow truck driver used to call from that location. Sigh: after talking to a friend who lives in Mullin, TX (also out in the boonies, not too far from our breakdown location, in fact) I learned that AT&T’s coverage in that part of Texas is much better than Verizon’s (the provider from whom Spectrum purchases their nationwide coverage). Good to know! Now you know, too…

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

22572 Explorer Tabs Causing Problems

Leave a comment

Wow! When I read about the new tabbing mechanism in Windows Explorer in the latest Dev Channel build, I couldn’t wait to try them out. Alas, they appear broken on both of my test PCs. In fact, they don’t behave at all as described in recent articles from WinAero and WindowsLatest. On those PCs, alas, 22572 Explorer tabs causing problems is the best I can describe my own experience.

What 22572 Explorer Tabs Causing Problems Means (to Me)

My symptoms are as follows:

1. I don’t see the iconography and layout that the afore-cited stories show. Instead i get a duplicated and somewhat mixed-up title bar:

22572 Explorer Tabs Causing Problems.dup-titles

Click item for full-sized view to show garbled text at left in upper nav/title bar, with lower nav/title bar beneath.

2. As I try to use the control keys for tabs (CTRL+T, CTRL+W, etc.) File Explorer crashes pretty regularly. While creating new tabs (CTRL+T) does something, it does not create tabs across the top of the UI as you’d expect it to. Closing tabs (CTRL+W) is as likely to crash Explorer as it is to close the duplicate title bar. Other tab controls (CTRL+Shift+Tab, etc.) do nothing visible.

3. I can use only the “lowest title bar” (the bottom one) actively. The others do not respond to mouse or keyboard activity.

Both of my test PCs look and behave exactly the same way. I’m tempted to do a clean install (or spin up a pristine VM) to see if that fixes things. But I don’t have time to do that today (other tasks loom large on my schedule. Sigh).

Something’s Busted…

It seems clear that further work is needed from MS to get things straightened out. Or, it could be, I’ve hit some kind of fatal interaction with something else I have installed on my test PCs. I’m hoping I’m not the only Insider who’s experiencing these difficulties. Otherwise, my life is about to get a whole lot more interesting.

We’ll have to wait and see what kinds of reports come in from other 22572 users. Rest assured, I’ll be keeping a close watch on this to see what’s happening, and what’s reported, around the symptoms I’m seeing

 

 

 

Facebooklinkedin
Facebooklinkedin
Backup/Restore, Insider stuff, Recent Activity, Tips, Tricks and Tweaks, USB devices, WED Blog, Windows 11

Quick Win11 Reghack Shows Removables Recycle Bin

Leave a comment

Here’s an interesting item that shows off a difference between Windows 10 and 11. Adding a specific Registry key and value to Windows 11 lets it show the recycle bin (and contents) in File Explorer on removable drives.  Normally (and on Windows 10) it doesn’t appear. A quick Win11 Reghack shows removables recycle bin.

That said, the same hack produces no visible sign of the Recycle Bin in Windows 10 File Explorer. Here’s what one of my 8 GB USB 3 removables looks like therein:

Quick Win11 Reghack Shows Removables Recycle Bin .win10

Notice there’s no entry shown named “Recycle Bin.” But as the lead-in graphic shows, it’s defined, even if it’s not visible.

When Quick Win11 Reghack Shows Removables Recycle Bin, Here’s What’s Shown

After adding a registry key named Explorer to

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\

One must create a DWORD therein named

RecycleBinDrives

Then that DWORD must be assigned the hexadecimal value “ffffffff” (all 1s for all 8 possible hexadecimal digits). Next comes a quick restart to make sure the setting “takes” in the Registry.

Presto! Recycle Bin Appears

As shown in the next screencap (from my X1 Extreme “road laptop”), you can now see the Recycle Bin (and System Volume Information) in the items listed in Explorer. (Note: for these items to appear, File Explorer Options/View must check “Show hidden files…” amidst its settings. As you can see, I also like to uncheck “Hide extensions…”)

Now you can see Recyle Bin and System Volume Info on the USB drive. Good-oh!

Why is access to Recycle Bin a good thing? Because it provides a ready means to recover deleted files from a USB drive directly, if one so desires. I agree with Sergey Tkachenko at WinAero.com (the source for this story and its info, though I had to create the Explorer key from scratch on my test PC) that easy recovery of deleted files can sometimes be a lifesaver!

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

22H2 Makes Nomenclature Debut

Leave a comment

Here’s an interesting tidbit for the sharp-eyed among us. A close look at a recent Windows 11 Cumulative Update (CU) is more revealing than most. As you can see in the lead in graphic, KB5102427 includes “version 22H2 Insider Preview” amidst its verbiage. Believe it or not, this is where 22H2 makes nomenclature debut from Microsoft. Sure, lots of people have been calling the “next release” of Windows 11 22H2 informally. AFAIK, this is the first “official” use of that term from MS.

If 22H2 Makes Nomenclature Debut, Then What?

Now we can refer to the upcoming release with improved confidence that the name is set. That said, MS has been known to change things up before public release. Thus, my use of “improved confidence” rather than something more absolute.

According to WindowsLatest (my source for this careful observation), MS also used this terminology  earlier, but in various  “leaked documents.” Like me, they read this appearance the 22H2 name as a first official sighting of this term in public use.

22H2 Covers Half the Year…

And indeed, it’s important to remember that 22H2 runs from July 1, 2022 through December 31, 2022. That gives MS a huge timeslot into which it can slide this upcoming release. Will the actual “go-public” date be closer to July or to December? Good question!

If history is any guide, October seems to be the most likely month. It’s been a fairly predictable time harking back to the twice-a-year regimen that used to prevail for the majority of Windows 10 releases. But with Windows 10 still in production through — you guessed it — October 2025, MS may decide to stagger Windows 11 releases to one side of that month or the other so as to avoid stacking both OSes up together.

On the other hand, MS has been pretty consistent about keeping more minor and monthly 10 and 11 releases more or less in lock step until now. Frankly this could go either way. I’m thinking it’s possible that 22H2 Windows 11 may show up earlier than its Windows 10 counterpart. But I’m also thinking it’s possible they could continue to travel together. Stay tuned: I’ll do my best to keep you  informed.

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

Bringing AMD PC Into Windows 11

Leave a comment

Man! What a day yesterday turned out to be. I finally had all the pieces together — or so I thought — to finish the AMD Ryzen 7 5800X PC. On the path to making that happen, and getting Windows 11 installed, I learned more than I expected. A LOT more… Bringing AMD PC into Windows 11 proved more difficult and challenging than I’d ever dreamed. Let me explain…

Parts Needed When Bringing AMD PC Into Windows 11

I finally broke down and ordered an Nvidia 3070 Ti GPU for the new build. I didn’t realize, until it showed up and I measured it against the Antec 902 case, that that darned thing was TOO BIG to fit inside. As my first such card, I didn’t know it needed about 2cm (around an inch) of additional clearance between the PCIe slot (and rear of the case where the outputs go) and the HDD cages at the front. Ouch!

So here’s what I had to do. My old Z170 (vintage 2017) build is in a monster Rosewill case with massive clearance. It housed an Nvidia 1070 Ti which I swapped out with the new 3070 Ti. Fortunately, the Corsair 750 PSU in the Rosewill case had enough power connectors for me to plug in 2x 8-pin power plugs to make that beast happy.

On the Antec side, I shoehorned the old 1070 Ti in. Even so, I endured some “cable snarl” to put everything in place. I had to use a tiny cable tie to hold the Reset, Power, and HD Light cablets together. Then, I used a “mosquito” (a tiny hemostat, very helpful for working inside tight spaces inside PCs) to plug them in together.

Other contortions were involved:

  • Went through a card slot at the back of the case to plug the HD97 audio connector in.
  • Used two HD power cables to reach each of 2 hard disks, to work around the 1070 GPU.
  • Used all but one of the power cables from the build’s Seasonic 650W PSU (first time ever for such a situation).

Power, Lights and Action…?

Eventually, I had all the parts together and mouse, keyboard and monitor plugged in. This time, when I hit the power switch the PC booted right into the Ventoy drive I had plugged into one of the USB 3.2 ports. I jumped immediately into installing Windows 11, only to be informed that the PC didn’t meet the necessary hardware requirements after getting past the “request for product key” screen.

Turns out that although the B550 Extreme4 motherboard and its Ryzen 5800X do support fTPM, they won’t do so unless it’s enabled in the UEFI. Figuring that out and fixing it turned into another series of adventures. They will serve as the basis for tomorrow’s story. Stay tuned, and I’ll tell you all about it then.

For now, I’m happy to report that the machine is running nicely at my second desk here in the office. I still have some setup work to do. Mostly that consists of installing a bunch of utilities, Macrium Reflect, Office 365, and then tweaking things just the way I like them. That should provide the basis for yet another story later this week. Cheers!

Facebooklinkedin
Facebooklinkedin
Uncategorized

Windows Reset Data Wipe Sometimes Falls Short

Leave a comment

For some time now, Windows has included a “Reset this PC” option. Among other uses, it lets sellers provide buyers with a pristine OS installation on used PCs. Or so runs the theory, when the “Remove everything” option is elected. However, researchers have observed that Windows reset data wipe sometimes falls short of this goal. Let me explain…

[NOTE: the lead-in graphic above shows what “Reset this PC” looks like in Windows 10 (above) and Windows 11 (below).]

How Windows Reset Data Wipe Sometimes Falls Short

Two data sources sometimes persist after running “Reset this PC” using the “Remove everything” option:

1. Windows.old remains behind. It includes all kinds of sensitive or interesting data about prior users.
2. When local OneDrive file copies exist, they could persist after the reset.

This info appears in the February 24 edition of Microsoft’s Windows 11 Known Issues. Indeed, there’s a section entitled “Files might persist after resetting a Windows device.” It reports which Windows versions manifest this failing: Windows 11, version 21H2;  and Windows 10, versions 21H2, 21H1 and 20H2.

What Known Issues Says

Here’s a verbatim quote from that page:

When attempting to reset a Windows device with apps which have folders with reparse data, such as OneDrive or OneDrive for Business, files which have been downloaded or synced locally from OneDrive might not be deleted when selecting the “Remove everything” option. This issue might be encountered when attempting a manual reset initiated within Windows or a remote reset. Remote resets might be initiated from Mobile Device Management (MDM) or other management applications, such as Microsoft Intune or third-party tools. OneDrive files which are “cloud only” or have not been downloaded or opened on the device are not affected and will not persist, as the files are not downloaded or synced locally.
Helpfully, two known fixes address these issues. First, disconnect from or disable OneDrive before initiating the reset. Second,  remove Window.old after reset completes. Taking these two simple steps ensures no personal info survives reset . Worth remembering!

For more information…

Use Disk Cleanup (or some useful analog like TheBookIsClosed’s Managed Disk Cleanup) or Storage Sense to remove Windows.old from a Windows PC. Indeed, MS provides a helpful how-to link for that latter operation.

Signing out of, or unlinking from, OneDrive before the reset operation prevents local OneDrive files from hanging ’round. Likewise, MS provides an equally helpful how-to link for this maneuver, too.

MS plans fixes for these shortcomings. In the meantime, if you simply disconnect from OneDrive before the Reset, then remove windows.old afterward, you’re covered. Good to know!

Note Added March 9, 2022: Issues Fixed (with Caveat)

With the release of Patch Tuesday fixes for Windows 10 and 11 yesterday (KB5011487 for 10; KB5011493 for 11) MS has fixed these “file hangover” problems. That said, both announcement include this language:

Some devices might take up to seven (7) days after you install this update to fully address the issue and prevent files from persisting after a reset. For immediate effect, you can manually trigger Windows Update Troubleshooter using the instructions in Windows Update Troubleshooter.

Thanks to Mary Jo Foley at ZDNet for bringing this to my attention.

 

Facebooklinkedin
Facebooklinkedin
Uncategorized

Build 22563 Makes Advanced Startup MIA

Leave a comment

Over the past couple of weeks, I’ve observed something odd and interesting. Many of my Windows 11 PCs were missing the Advanced Startup option. Ordinarily, it’s in Settings → System → Recovery → Recovery Options. Just yesterday, undeniable curiosity let me observe that Build 22563 makes Advanced Startup MIA again. This time, I’m NOT going to create an ISO and run an in-place upgrade repair install. Though I think it would fix it, I won’t do that this time. Instead, I’m convinced this needs reporting to Feedback Hub as a recurring problem.

Build 22563 Makes Advanced Startup MIA Again: FB Hub Report In

I upvoted and added to a thread on the Feedback Hub entitled “The Advanced Startup option is missing from the recovery menu.” I’m now convinced this is a recurring problem that can occur when upgrading an Insider Preview to a new Insider Build, or when applying a Cumulative Update to an RTM Build. I’ve had it happen on 3 of my 5 Windows 11 machines in the last week, in fact. That’s disheartening, after spending a half-day repairing the issue. See my Feb 21 post about the fix for all those gory details.

But now, I know there’s a problem across the board in Windows 11. The only thing I don’t know is if the problem is just across the board on MY Windows 11 PCs, or more of them than that. That’s why I’m reporting to Feedback Hub and hoping for results. Peferably, sooner rather than later. We’ll see.

I will observe that my lone “native Windows 11” PC seems immune to this issue. All of my other Windows 11 PCs were (a) upgraded from 10 to 11, and (b) regularly manifest this issue. I’d be curious to understand the connection, if any, that might be involved…

Facebooklinkedin
Facebooklinkedin