Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, August 10, 2016 11:00 AM | 1 vote
Hello,
After updating my system to the Anniversary Update I decided to try this new feature. But unfortunately I can't find Quick Assist in Start menu, also there is no quickassist.exe file in %windir%\system32.
Do you know how to fix this?
2016.09.14 Update: I remembered that I deleted Quick Assist from optional components. Is there any way to restore it without reinstalling windows.
**2017.04.11 Update 2: **It is restored after upgrading to Creators Update
All replies (45)
Wednesday, August 10, 2016 11:17 AM | 1 vote
Type Command Prompt in the Search box, right-click Command Prompt, and then click Run as administrator.
At the command prompt, type the following command, and then press ENTER:
sfc /scannow
I shall also suggest you to update your system via Windows update. This will allow your system to be updated to 14363.67. Hopefully it will fix the problem.
S.Sengupta, Windows Insider MVP
Wednesday, August 10, 2016 11:59 AM | 1 vote
As I understand 14363.67 released only to Insiders. I am on latest release build 14363.51. Already tried sfc /scannnow without any success.
Thursday, August 11, 2016 3:05 AM | 1 vote
Open the following location:
C:\WINDOWS\system32
Now try to locate quickassist. Is it there?
S.Sengupta, Windows Insider MVP
Thursday, August 11, 2016 5:28 AM | 1 vote
Hi Ja66y,
First of all, please ensure the machine has got the latest updates.
I have checked that tool on my Windows 10.14393.51 Enterprise machine and that tool was available. Run "Winver" to check present version.
"Already tried sfc /scannnow without any success."
Did the sfc /scannow find any errors?
Please try to run "dism /online /cleanup-image /restorehealth" to check the system health, too.
Best regards
Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Thursday, August 11, 2016 8:24 AM | 1 vote
Open the following location:
C:\WINDOWS\system32
Now try to locate quickassist. Is it there?
S.Sengupta, Windows Insider MVP
As I wrote before, there is no quickassist.exe file in %windir%\system32
Thursday, August 11, 2016 9:03 AM | 1 vote
As I said before, I am on the latest release version 14393.51.
Output from: sfc /scannow
C:\WINDOWS\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
Output from "dism /online /cleanup-image /restorehealth"
C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.14393.0
Image Version: 10.0.14393.0
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
And still no success.
Friday, August 12, 2016 8:26 AM | 1 vote
Hi Ja66y,
What is the exact environment (domain or home)? How did you update to 1607? Are you using a Home version, Pro or Enterprise version?
Best regards
Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Monday, August 15, 2016 10:41 PM | 1 vote
Hi, sorry for late reply. I am using Pro version at home, so no domain. I've updated using windows update.
Tuesday, August 16, 2016 7:27 AM | 1 vote
Hi Ja66y,
I have checked both on my Windows 10 Enterprise and Home version. The "Quick Assis" application is there. You may try to perform an in-place upgrade repair with the latest Windows 10 ISO(If you have downloaded one before, try to download a new one). Boot from the ISO and choose "Upgrade" install.
Windows 10 ISO
https://www.microsoft.com/en-au/software-download/windows10
Best regards
Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Friday, August 26, 2016 7:08 AM | 1 vote
Hi,
How about the issue, is there anything to update?
Best regards
Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Tuesday, September 6, 2016 2:59 PM | 1 vote
Hi, I have a similiar issue.
I deleted Quick Assist from the "optional features" and now I am not able to reinstall it.
I did some searches and looks like that "quick assists" is completely missing from the DISM catalog: if I type "dism /online /get-capabilities" the quck assist package, along side with contact support, are completely missing from online packages.
There should be two packages named App.Support.ContactSupport0.0.1.0 and App.Support.QuickAssist
SFC /scannow and DISM restore commands do not help at all.
Wednesday, September 14, 2016 2:08 PM | 1 vote
Now I am pretty sure that the same happened to me. As I remember I deleted some stuff from optional components.
Sunday, September 18, 2016 1:29 PM | 1 vote
Anyone got a solution already? Uninstalled it also and can't find a way to reinstall it.
Sunday, September 18, 2016 1:56 PM | 1 vote
Settings > System > Apps & features then Manage optional features. Add a feature, listed as Microsoft Quick Assist.
Sunday, September 18, 2016 2:06 PM | 1 vote
I uninstalled it there. But I can't install it again because the option is not available anymore after an uninstall.
Sunday, September 18, 2016 2:32 PM | 1 vote
Can you check it was not added back in via an update? I ask as that was in add features for me before I removed it. I only removed it after reading this thread. The program will be in C:\Windows\System32 just in that folder as quickassist.exe or shows in the start under Windows Accessories.
If not what version and what build of Windows 10 are you running?
Sunday, September 18, 2016 2:50 PM | 1 vote
Windows version is 1607 (with latest patches etc). It's unfortunately not installed with an update. Also there's no quickassist.exe available on my system anymore (did a full system search).
Sunday, September 18, 2016 10:25 PM | 1 vote
Ok interesting, so login local or MS?
As me thinking of things to try, from a PowerShell prompt;
Get-AppXPackage -Name windows.immersivecontrolpanel | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml" -Verbose}
Reregisters the settings. See if that helps.
Monday, September 19, 2016 9:45 AM | 1 vote
Settings > System > Apps & features then Manage optional features. Add a feature, listed as Microsoft Quick Assist.
I do not have it in the optional features. I also do not have it under dism /online /get-capabilities at all.
Monday, September 19, 2016 6:14 PM | 1 vote
Didn't help unfortunately. My login is with an outlook.com account.
Monday, September 19, 2016 9:45 PM | 1 vote
Well out of ideas really (beyond a repair install \ clean install). So perhaps someone else has something to offer.
Wednesday, September 21, 2016 8:52 AM | 1 vote
Hi Ja66y,
I made a test on my machine. It shares the same symptom as yours. But I found a workaround. I tried to copy the "Quickassist.exe" (it is a desktop app) from another machine and it could work well, too.
Best regards
Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Thursday, September 22, 2016 5:28 PM | 1 vote
Copying the file doesn't work unfortunately. Gives an error message when trying to run it after copying. So it probably needs some libraries or registry settings.
Friday, November 11, 2016 5:50 PM | 1 vote
Quick Assist should be able to be reinstalled via:
dism /Online /Add-Capability /CapabilityName:<name> /Source:<mount point>
- ** /CapabilityName** would be the full version name of Quick Assist App.Support.QuickAssist~~~~0.0.1.0
- /Source would be the mounted install.esd from a v1607 Windows install ISO (ensure correct index for your version of windows is mounted from install.esd, as each contains 4 images)
dism /Online /Add-Capability /CapabilityName:App.Support.QuickAssist~~~~0.0.1.0 /Source:Z:/Mount
/restorehealth and /scannow are two sides of the same coin and must be run in the proper order
1. dism /online /cleanup-image /restorehealth must be run prior to running /scannow
- /restorehealth verifies cab files within the WinSxS folder have not become corrupted by matching hashes from Windows Update servers; if corruption is found, it replaces the applicable cab files with originals downloaded from Windows Update [or a mounted image if /source is utilized]. WinSxS contains a copy of every Windows system file, allowing the system to fix itself
2. sfc /scannow must be run after running /restorehealth
- /scannow verifies all system files match the hashes of their originals within the WinSxS folder; if corruption is found, SFC replaces the corrupted file with the original contained within the applicable WinSxS cab file.
There will be times when /restorehealth fails due to the component store within WinSxS containing two or more different versions of an applicable cab, which occurs when an inplace upgrade or update did not properly cleanup after itself. If this occurs, run /dism /online /cleanup-image /StartComponentCleanup, restart, then re-run /restorehealth.
Saturday, November 12, 2016 8:23 AM | 1 vote
Not working for me:
C:\WINDOWS\system32>dism /Online /Add-Capability /CapabilityName:App.Support.QuickAssist~~~~0.0.1.0 /Source:D:/Sources
Deployment Image Servicing and Management tool
Version: 10.0.14393.0
Image Version: 10.0.14393.0
Error: 87
No Windows features were specified on the command line.
Use the /Get-Features option to find the name of the feature in the image and try the command again.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
Wednesday, March 8, 2017 11:58 PM | 1 vote
So once you remove it, you can't get it back?
Seems like a bug. Maybe Microsoft will fix this in the Creator's update next month.
Tuesday, April 11, 2017 1:14 AM | 1 vote
I figured it out. You'll need the Windows 10 v1607 ISO (or install.wim specifically).
Do the following:
Mount the install.wim from the Sources directory in the ISO. (I'll refer to this as C:\WIM)
Create a new, empty working directory (I'll refer to this as C:\QA)
Copy these [40] directories from C:\WIM\Windows\WinSxS\amd64_microsoft-windows-quickassist* to C:\QA
Copy these [41] files from C:\WIM\Windows\WinSxS\Manifests\amd64_microsoft-windows-quickassist* to C:\QA
Copy these [2] files from C:\WIM\Windows\Servicing\Packages\Microsoft-Windows-QuickAssist-Package* to C:\QA
Rename the C:\QA\.cat file to update.cat
Rename the C:\QA\.mum file to update.mum
You can un-mount the wim now; you are done with it.
Create a text file (I'll call it unat.xml) with the following contents:
<?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="install"> <assemblyIdentity name="Microsoft-Windows-QuickAssist-Package" version="10.0.14393.0" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="" /> <source location="C:\QA"/> </package> </servicing> </unattend>Copy the C:\QA folder to a local drive on the computer and run this command:
dism.exe /Online /Apply-Unattend:unat.xmlThat should do it.
-Tony
Wednesday, April 19, 2017 11:31 PM | 1 vote
Tony,
Looking at the SOURCES directory in the 1607 (Pro) ISO, there is no INSTALL.WIM. There's an INSTALL.ESD. Can you elaborate...and verify that your procedure succeeds?
A reinstall from the ISO (keep files) did not reinstate Quick Assist.
Thursday, April 20, 2017 5:45 AM | 1 vote
Tony,
Looking at the SOURCES directory in the 1607 (Pro) ISO, there is no INSTALL.WIM. There's an INSTALL.ESD. Can you elaborate...and verify that your procedure succeeds?
A reinstall from the ISO (keep files) did not reinstate Quick Assist.
I can confirm that my instructions work. In fact, I followed them yesterday to install Quick Assist on Windows 10 2016 LTSB (which doesn't include Quick Assist).
I don't know why some distros have the ESD instead of a WIM. I've only seen it on ISOs made by the Microsoft Media Creation Tool.
Anyway, you just need to convert the ESD to a WIM, then follow the instructions I listed.
This Spiceworks article explains how to convert the ESD to WIM.
To mount a WIM:
dism /mount-image /imagefile:D:\sources\install.wim /index:1 /mountdir:C:\wimmount
To unmount a WIM:
dism /unmount-image /mountdir:c:\wimmount /discard
-Tony
Thursday, April 20, 2017 10:16 PM | 1 vote
Tony, here's how it went.
Converted the INSTALL.esd to INSTALL.wim and placed it in C:\
Created C:\QA and copied...
Every folder named Quick Assist from AMD64. There were 39, not 40.
Every file named Quick Assist from Manifests. There were 40, not 41. And QuickAssist.exe was also copied. See them at http://hevanet.com/hb/QA.zip.
Perhaps the discrepancy in the number of folders is that this was a 1703 ISO restore to a HOME 1703PC, not 1611?
If this material is not version specific please copy your QA pkgs and link them here.
Lastly, two folders from Servicing/Pkgs that were named Quick Assist were copied. Renamed them update.cat and update.mum. There were actually four with a Quick Assist designation, also with .cat and .mum extensions, but the other two had WOW64 in their paths.
Unmounted the WIM file.
Created the "unat.xml" from a Notepad text file and placed it in C:\
Brought up the elevated CMD prompt in the C:\ directory and ran
dism.exe /Online /Apply-Unattend:unat.xml. This was the file...
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<servicing>
<package action="install">
<assemblyIdentity name="Microsoft-Windows-QuickAssist-Package" version="10.0.14393.0" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="" />
<source location="C:\QA"/>
</package>
</servicing>
</unattend>
Result: "The data is invalid." Also tried the command after substituting the two (.cat & .mum) files that had WOW64 in their names into C:\QA. Still no joy.
Didn't quite understand step #10, "Copy the C:\QA folder to a local drive on the computer..." since it already existed on C:\ So that wasn't done.
Here's the log: http://hevanet.com/hb/DISM_log.txt Perhaps it will give a clue as to what went wrong.
What is most confounding is why a fresh install (keep files), made from an Media Creation Tool ISO on the same PC did not reinstate QA. Should have "don't keep files" been specified? Is there a BIOS setting issue?
Best regards, and thanks for your time.
Saturday, April 22, 2017 12:41 AM | 1 vote
Every folder named Quick Assist from AMD64. There were 39, not 40.
Every file named Quick Assist from Manifests. There were 40, not 41. And QuickAssist.exe was also copied. See them at http://hevanet.com/hb/QA.zip.Perhaps the discrepancy in the number of folders is that this was a 1703 ISO restore to a HOME 1703PC, not 1611?
Yes, my instructions were for Windows v1607 x64. For v1703, things are a little different:
- There are 39 WinSxS folders and 40 manifest files.
- There are 4 files in the serving folder (2 x .cat and 2 x .mum). You need to copy all four.
- You should rename the files without WOW64 in the name to update.*
- You don't need the quickassist.exe file in the root (it's in one of the folders you copied).
Using your zip file as a reference, simply delete the quickassist.exe file and add the 2 WOW64 files.
Created the "unat.xml" from a Notepad text file and placed it in C:\
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<servicing>
<package action="install">
<assemblyIdentity name="Microsoft-Windows-QuickAssist-Package" version="10.0.14393.0" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="" />
<source location="C:\QA"/>
</package>
</servicing>
</unattend>Result: "The data is invalid."
For Windows v1703, the version number is different. Use this unat.xml:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<servicing>
<package action="install">
<assemblyIdentity name="Microsoft-Windows-QuickAssist-Package" version="10.0.15063.0" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="" />
<source location="C:\QA"/>
</package>
</servicing>
</unattend>
Didn't quite understand step #10, "Copy the C:\QA folder to a local drive on the computer..." since it already existed on C:\ So that wasn't done.
Yes, you are correct. This was meant for if you were using another PC.
What is most confounding is why a fresh install (keep files), made from an Media Creation Tool ISO on the same PC did not reinstate QA. Should have "don't keep files" been specified? Is there a BIOS setting issue?
I don't think the "don't keep files" option would make a difference, but I'm not 100% sure. The BIOS has no affect here, so no BIOS setting issue. Probably just a Microsoft issue :)
I read somewhere that starting with 1703, Windows will not automatically reinstall components you've removed during upgrades (this is a real pain for network admins). Maybe that's why it was not reinstalled. But I thought I read the change started with upgrading from 1703 to something newer, so it didn't apply yet? Again, not sure about that article I glanced at sometime ago.
-Tony
Sunday, April 23, 2017 4:31 PM | 1 vote
Tony, Gave it a go...
In C:\QA there are 39 AMD64 folders; 40 manifest files; 2 cat/mum files respectively; 2 WOW64 files.
Ran the elevated command prompt with...
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<servicing>
<package action="install">
<assemblyIdentity name="Microsoft-Windows-QuickAssist-Package" version="10.0.15063.0" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="" />
<source location="C:\QA"/>
</package>
</servicing>
</unattend>
Also tried changing the "10.0.15063.0" to "10.0.15063.138" to reflect the winver shown on the PC.
Result: "The referenced assembly could not be found.
Well, at least the error message is different.
I've posted the revised QA zipped folder to http://hevanet.com/hb/QA.zip
The DISM log is here... http://hevanet.com/hb/DISM.log. In that log, you will spot four failure/warning lines. So dang close. ^_^
Your continued enlightenment is welcomed, Gracias
Monday, April 24, 2017 6:20 AM | 1 vote
Tony, Gave it a go...
In C:\QA there are 39 AMD64 folders; 40 manifest files; 2 cat/mum files respectively; 2 WOW64 files.
Ran the elevated command prompt with...
<?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="install"> <assemblyIdentity name="Microsoft-Windows-QuickAssist-Package" version="10.0.15063.0" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="" /> <source location="C:\QA"/> </package> </servicing> </unattend>Also tried changing the "10.0.15063.0" to "10.0.15063.138" to reflect the winver shown on the PC.
Result: "The referenced assembly could not be found.
Well, at least the error message is different.
I've posted the revised QA zipped folder to http://hevanet.com/hb/QA.zip
The DISM log is here... http://hevanet.com/hb/DISM.log. In that log, you will spot four failure/warning lines. So dang close. ^_^
Your continued enlightenment is welcomed, Gracias
The version must match the version of the package you are installing, not the version of Windows. The version is specified in the .mum file and is also in the name of each file/folder. That's where I got 10.0.15063.0 -- that's definitely right.
Your zip file looks good.
The dism.log file you provided is not from a dism /online /apply-unattend command, so it's no help.
Try it again with the correct version in the unattend file, and post the dism.log.
-Tony
Monday, April 24, 2017 2:22 PM
Hello Tony,
10.0.15063.0 was tried first. .138 was added only after the initial attempt failed, as it continues to do: Referenced assembly could not be found. The .mum file version lists 10.0.15063.0.
The QA folder and the unat.xml file are both in C:\ The command being from the elevated C:\ prompt is your specified
dism.exe /Online /Apply-Unattend:unat.xml
A disc search for DISM.log returns only the one that I have posted, now updated after the latest failure. The same four warning/failure lines are shown, and I note that one states that "c:\windows may not point to a valid Windows folder." That's strange.
If there's a route to another DISM log, please list the path/command line.
My friend and I thank you for seeing this through. He may wind up with Team Viewer. ^
Monday, April 24, 2017 7:41 PM
Hello Tony,
10.0.15063.0 was tried first. .138 was added only after the initial attempt failed, as it continues to do: Referenced assembly could not be found. The .mum file version lists 10.0.15063.0.
The QA folder and the unat.xml file are both in C:\ The command being from the elevated C:\ prompt is your specified
dism.exe /Online /Apply-Unattend:unat.xmlA disc search for DISM.log returns only the one that I have posted, now updated after the latest failure. The same four warning/failure lines are shown, and I note that one states that "c:\windows may not point to a valid Windows folder." That's strange.
If there's a route to another DISM log, please list the path/command line.
My friend and I thank you for seeing this through. He may wind up with Team Viewer. ^
The dism.log you uploaded today looks correct. Previously, it contained details of disk cleanup, or something.
The dism.log, line 111, indicates that CBS returned code 0x80073701 – ERROR_SXS_ASSEMBLY_MISSING. The errors begin immediately after that.
So, look at the C:\windows\logs\cbs\cbs.log for details.
As a test, I installed v1703 Pro x64 from ISO on a clean PC, and uninstalled Quick Assist using:
dism.exe /Online /Apply-Unattend:unat.xml
with unat.xml:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<servicing>
<package action="remove">
<assemblyIdentity name="Microsoft-Windows-QuickAssist-Package" version="10.0.15063.0" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="" />
</package>
</servicing>
</unattend>
I then downloaded your QA.zip, extracted it to C:\QA and reran dism using the unat.xml you listed. It worked fine. So, your QA folder is good.
You need to dig deeper by looking at the cbs.log, but I'm not very knowledgeable on that.
-Tony
Monday, April 24, 2017 10:17 PM
Tony,
It's good that you confirmed the integrity of the QA file. Everything you have done appears to have been duplicated here.
While you may not be a CBS analyst, perhaps another interested and knowledgeable user will drop by to help us all make sense of it what causing the hang up on this laptop.
Here is the CBS.log file.
I assume that it makes no difference whether the user is signed into an MS account (which is the case) or a local account.
Thanks again for your conscientious and responsive effort!
Monday, April 24, 2017 11:16 PM
Hmm. Comparing your cbs.log and mine, they are the same until line 36, where you get this error:
(F) onecore\base\wcp\componentstore\csd_locking.cpp(95): Error STATUS_SXS_ASSEMBLY_MISSING originated in function CCSDirectTransaction::LockComponent expression: (null)
It's like it can't find the source. Let's try something else...
Mount up the install.wim file and let's add some more items to C:\QA:
- Copy these [39] directories from C:\WIM\Windows\WinSxS\wow64_microsoft-windows-quickassist* to C:\QA
- Copy these [39] files from C:\WIM\Windows\WinSxS\Manifests\wow64_microsoft-windows-quickassist* to C:\QA
So, now C:\QA will have 78 folders, 79 manifest files, and the 4 servicing files (two renamed).
Try to install it again.
-Tony
Tuesday, April 25, 2017 3:05 AM
What a battle! (And what a thread.)
"The referenced assembly could not be found."
The updated CBS.log file. The updated QA.zip file.
Could the problem be a Windows setting, a missing directory, permissions, the phase of the moon?
Send a bill, Tony. ^
Tuesday, April 25, 2017 3:28 AM
What a battle! (And what a thread.)
"The referenced assembly could not be found."
The updated CBS.log file.
Could the problem be a Windows setting, a missing directory, permissions, the phase of the moon?
Hmm, well maybe there is something wrong with the Windows installation. Try running these commands to detect/repair Windows problems (they shouldn't break anything and should be safe to run on any computer):
chkdsk c: /f
sfc /scannow
dism /online /cleanup-image /restorehealth
If it still doesn't work, it may be time to reinstall Windows. Or, that's what I would do, but I reinstall Windows yearly anyway, so it's no big deal to me. You'll have to make that call for yourself.
Send a bill, Tony. ^
lol. :)
Good luck.
-Tony
Tuesday, April 25, 2017 4:54 AM
Chkdsk /f and SFC are clean. RestoreHealth "can't find the source files" ... but from what I have read, this is a known issue in 1703. I doubt there's a problem.
My friend says he is not certain whether QA ever functioned. He recalls that the code would flash momentarily when he attempted to give assistance. So we deleted QA. Probably a bad move.
We then RESET W10. No QA.
Next we reverted to 1607. No QA. I see that there's a manufacturer's recovery partition, but this procedure may not have used it. When <alt-F10> was pressed, per ACER recovery instructions, it brought up the W10 recovery options screen, which offered the reset choice we'd already tried.
No QA in 1607, and an update to 1703 via the Windows 10 upgrade assistant didn't do any better.
Finally we downloaded the ISO with the MS Media Creation Tool and reinstalled (keeping files). Likely the same process as the prior update.
Perhaps a reformatting and resinstall would do the job, but there comes a time when it isn't worth the effort. Friend can either use Team Viewer or return the machine, which is still under 90-day warranty, and start anew. There's little in the way of programs and customization at this point.
Again, appreciative of all your efforts, Tony. Some things were never meant to be known.^_^
Friday, July 28, 2017 7:31 PM
To reinstall Quick Assist on Windows 10 v1703:
You'll need the Windows 10 v1703 install.wim file.
Mount the install.wim from the Sources directory in the ISO. (I'll refer to this as C:\wim)
Create a new, empty working directory (I'll refer to this as C:\QuickAssist-FOD)
Copy these [39] directories from C:\wim\Windows\WinSxS\amd64_microsoft-windows-quickassist* to C:\QuickAssist-FOD
Copy these [39] directories from C:\wim\Windows\WinSxS\wow64_microsoft-windows-quickassist* to C:\QuickAssist-FOD
Copy this file from C:\wim\Windows\WinSxS\Manifests\amd64_microsoft-windows-q..st-wow64* to C:\QuickAssist-FOD
Copy these [40] files from C:\wim\Windows\WinSxS\Manifests\amd64_microsoft-windows-quickassist* to C:\QuickAssist-FOD
Copy these [39] files from C:\wim\Windows\WinSxS\Manifests\wow64_microsoft-windows-quickassist* to C:\QuickAssist-FOD
Copy these 4 files from C:\wim\Windows\Servicing\Packages\Microsoft-Windows-QuickAssist-* to C:\QuickAssist-FOD
Rename C:\QuickAssist-FOD\Microsoft-Windows-QuickAssist-Package~31bf3856ad364e35~amd64~~10.0.15063.0.cat to update.cat
Rename C:\QuickAssist-FOD\Microsoft-Windows-QuickAssist-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum file to update.mum
You can un-mount the wim now; you are done with it.
Create an unattend.xml file with the following contents:
<?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="install"> <assemblyIdentity name="Microsoft-Windows-QuickAssist-Package" version="10.0.15063.0" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="" /> <source location="C:\QuickAssist-FOD"/> </package> </servicing> </unattend>Copy the C:\QuickAssist-FOD folder to a local drive on the computer and run this command:
dism.exe /Online /Apply-Unattend:unattend.xmlDelete the C:\QuickAssist-FOD temporary folder
-Tony
Wednesday, September 5, 2018 3:40 PM
Thanks for the guide Tony. I got the following:
c:\QA>dism.exe /Online /Apply-Unattend:unat.xml
Deployment Image Servicing and Management tool
Version: 10.0.14393.0
Image Version: 10.0.14393.2457
[==========================100.0%==========================]
The operation completed successfully.
c:\QA>
But cannot find it installed anywhere. I'm using a 2016 LTSB image. I tried manage optional features but it is not there
Friday, September 21, 2018 5:42 PM | 2 votes
1. Copy the file from another computer. (Windows/System32/quickassist)
2. Put in the your system 32 folder
3. right click and click on properties.
4. Click on Compatibility tab
5. Click on Change settings for all users.
6. Check on the run this program compatibility mode for and select Windows 7
7. Check the Run this program as an Admin.
This workaround worked for me!!
Tuesday, December 31, 2019 9:20 AM
Run this command in PowerShell and its install back the QuickAssist applications
* Make sure the computer have access to Internet
dism /Online /Add-Capability /CapabilityName:App.Support.QuickAssist~~~~0.0.1.0
Tuesday, July 28, 2020 1:12 PM
This worked for me! I only uninstalled because I couldn't get logged in with my corporate MS account.