Can't get latest version of Quick Assist (2.0.8.0) to run

Ceelix · 29 Aug 2022

I suspect that this isn't solvable given all of my circumstances and such (I'm not on the latest Windows 10 for various reasons I don't want to get into here). I tried but I'm at a loss as to how to solve this. I'll probably just use Team Viewer.

I'm on Windows 10 Pro x64 2004:

Can't get latest version of Quick Assist (2.0.8.0) to run-winver.png

The old version of Quick Assist gives a message saying it needs to be updated using the Windows store. I did that, but, it continues to give a message saying it needs to be updated, even though it's at the current version - 2.0.8.0.

I don't use Microsoft Store, and have all of the removable apps uninstalled using O&O AppBuster. So, to get the latest version of QuickAssist, I did this:

I downloaded the latest (2.0.8.0) QuickAssist AppxBundle by going to the Microsoft Store and searching for Quick Assist, which gives this URL: https://apps.microsoft.com/store/det...hl=en-us&gl=US. I then pasted that URL here: store.rg-adguard.net, and downloaded the AppxBundle.

I then used the PowerShell script located here: droidkid.net/2022/05/17/powershell-script-to-install-the-new-quick-assist-silently. I renamed the above AppxBundle to MicrosoftCorporationII.QuickAssist.AppxBundle. That and the PowerShell script - Quick-Assist-Package.ps1, were in the same folder. I opened PowerShell on the folder and ran powershell -executionpolicy bypass -file Quick-Assist-Package.ps1 -install.

It worked, it uninstalled the old version of Quick Assist, and installed the new Windows Store version. I can run Get-AppxPackage | Select Name, PackageFullName in PowerShell and confirm that the latest Quick Assist is installed.

But when I try to run C:\Program Files\WindowsApps\MicrosoftCorporationII.QuickAssist_2.0.8.0_x64__8wekyb3d8bbwe\QuickAssist.exe, this is what I get:

Can't get latest version of Quick Assist (2.0.8.0) to run-quick_assist.png

Quick Assist shows a throbber screen at first (spinning dots), then gives the same message as before, "There's a new version of Quick Assist". Within 5 or so seconds, a "Background Task has stopped working" message box appears, then a second one within another few seconds.

I'm not familiar with Windows Store and won't use it, so I'm guessing this has to be run from Windows Store, and can't run like a regular (actual) application using a shortcut to the executable.

Is that right? Or is there some way it can work I'm missing here?

dalchina · 29 Aug 2022

I think you may be seeing what's described here:
Microsoft's replaces bundled Quick Assist app with Microsoft Store version - gHacks Tech News
- that Quick Assist (version ?) no longer works and has been replaced by a version exclusively from the Store.

As such, given all the restrictions you've placed on yourself, I doubt anyone's going to be able to help you other than to suggest using an alternative means of allowing remote access.

Ceelix · 29 Aug 2022

Yes that's it... Microsoft took a convenient light weight remote control option built into the OS and moved it to the Store. They claimed they did this for "security" reasons, but I think that's complete nonsense, since it could easily be updated through Windows Update. So far, most all Support and Admins agree that this shouldn't be a "Store" app... if someone had Windows 10, you could always "just use Quick Assist"... but no more. Most corporations that I know disable the Windows store on their LANs. Users now need admin rights to install the new "Store" version of Quick Assist. And because it now requires a user walkthrough just to get it installed, updated, and running, it's just not worth using for most people. The easiest option now is AnyDesk or TeamViewer.

Nonetheless, I'm still trying to see if there's a way to run the Windows Store version of Quick Assist without the Windows Store.

It doesn't look like it?

dalchina · 29 Aug 2022

Whilst it should in principle be possible to run an app without the Store installed, perhaps your difficulty now is actually getting a version (that is only available from the Store) to install.

I doubt anything here will help directly (there is the Powershell command to re-register it).
Four Methods to Fix Quick Assist Missing in Windows 10, 11

Anyviewer is mentioned at the end.

Could be worth exploring the links here to see if you can get the appropriate version, as the article seems to have been written after the change:
Windows admins frustrated by Quick Assist moving to Microsoft Store

You need Webview2 as well:
Get-Updated Quick Assist and WebView2 for Standard Users – TechNuggets

Ceelix · 29 Aug 2022

As I thoroughly explained, and showed in the screenshot, the app appears to be installed successfully.

pastebin.com/wmLYuSFp

Can't get latest version of Quick Assist (2.0.8.0) to run-appbuster.png

dalchina · 29 Aug 2022

Thank you for stating that so thoroughly.

Then you know what you're doing. Good luck!

Ceelix · 29 Aug 2022

dalchina said:

I doubt anything here will help directly (there is the Powershell command to re-register it).
Four Methods to Fix Quick Assist Missing in Windows 10, 11

Anyviewer is mentioned at the end.

Of course it is, that article is on AnyViewer's website.

dalchina said:

You need Webview2 as well:
Get-Updated Quick Assist and WebView2 for Standard Users – TechNuggets

Wow, this is the first I've seen this. I know I don't have that installed. Not sure if the Store would automatically install this if the user doesn't have it? If not, that makes the change for Quick Assist even more convoluted for people who need help ASAP.

So then, Quick Assist just appears to use the web browser. It would use Edge Chrome, not Edge HTML. I never installed Edge Chrome, because it seems to me, what's the point? It's Chrome, why not just use Chrome? Chrome already has a remote control app: remotedesktop.google.com/support

So there's little reason for anyone to bother with using Quick Assist now, since Microsoft basically crippled it, at least from its previous light weight, built-in form. It's also pretty bad IMHO that this was treated as a "service," as users cannot revert to the previous version, as it goes through Microsoft in order to work.

So I would have to install Edge Chrome, and Edge Webview2, and then maybe it will work.

I'll just stick to AnyDesk or TeamViewer.

Thanks for the replies.

RickC · 29 Aug 2022

Perhaps use Sysinternals/TechNet's Process Monitor (ProcMon), filtered on QuickAssist, to see what's failing?

For example:

Can't get latest version of Quick Assist (2.0.8.0) to run-procmon_quickassist1.png

(See The Ultimate Guide to Procmon for more info.)

Hope this helps...

Ceelix · 29 Aug 2022

Thanks for that, it did.

It appears that the x86 version of Edge Webview was installed when I ran the original PowerShell script: pastebin.com/SeiqgHT9.

Since I only have Edge HTML, not Edge Chrome, that may be why it doesn't work.

Here's the pastebin of the procmon: pastebin.com/BBkGA5Ts

Seems to be a lot of "NOT FOUND" errors, a lot of them on "CreateFile" in the application directory. Maybe a file security problem?

pastebin.com/eMf2vequ

- - - Updated - - -

x64dbg log, for what it's worth:

pastebin.com/G3DXaW3D

RickC · 29 Aug 2022

Ceelix said:

Seems to be a lot of "NOT FOUND" errors, a lot of them on "CreateFile" in the application directory. Maybe a file security problem?

IME, 'NOT FOUND' errors are commonplace. For example in your PasteBin post look at lines 582 and 583. 582 shows 'NAME NOT FOUND' for prio.ini in C:\Windows whilst 583 shows 'SUCCESS' in creating the prio.ini file immediately afterwards within the user's roaming profile. What's more interesting is that I couldn't see a single 'FAILURE' entry.

Ceelix said:

x64dbg log, for what it's worth:

pastebin.com/G3DXaW3D

I note the amount of 'The process has no package identity' entries. A Google search shows this Methods to Fix The Process Has No Package Identity Error Problem Issue article as the top returned result. Any use (particularly methods 2 and 3, with 3 being perhaps more relevant)?

Hope this helps...