Merge branch 'update-troubleshooting' of https://github.com/PROTechThor/qubes-doc into PROTechThor-update-troubleshooting

doc.md

@@ -132,6 +132,7 @@ Core documentation for Qubes users.
  * [Media Troubleshooting](/doc/media-troubleshooting/)
  * [Firewall Troubleshooting](/doc/firewall/#firewall-troubleshooting)
  * [VPN Troubleshooting](/doc/vpn-troubleshooting/)
+ * [Update Troubleshooting](/doc/update-troubleshooting/)
 
 ### Reference Pages
 

introduction/faq.md

@@ -441,12 +441,9 @@ It begins with an explanation of the risks with such a setup.
 
 See [here][version].
 
-### My qubes lost Internet access after a TemplateVM update. What should I do?
+### My qubes lost internet access after a TemplateVM update. What should I do?
 
-Run `systemctl enable NetworkManager-dispatcher.service` in the TemplateVM upon which your NetVM is based. 
+See [Update Troubleshooting](/doc/update-troubleshooting/#lost-internet-access-after-a-templatevm-update).
-You may have to reboot afterward for the change to take effect. 
-(Note: This is an upstream problem. See [here](https://bugzilla.redhat.com/show_bug.cgi?id=974811)). 
-For details, see the qubes-users mailing list threads [here](https://groups.google.com/d/topic/qubes-users/xPLGsAJiDW4/discussion) and [here](https://groups.google.com/d/topic/qubes-users/uN9G8hjKrGI/discussion).)
 
 ### My keyboard layout settings are not behaving correctly. What should I do?
 
@@ -607,34 +604,11 @@ From a `dom0` prompt, enter:
 
 ### When I try to install a TemplateVM, it says no match is found.
 
-For example:
+See [VM Troubleshooting](/doc/vm-troubleshooting/#no-match-found-when-trying-to-install-a-templatevm).
-
-```
-[user@dom0 ~]$ sudo qubes-dom0-update --enablerepo=qubes-templates-itl qubes-template-debian-10
-Using sys-whonix as UpdateVM to download updates for Dom0; this may take some time...
-No Match for argument qubes-template-debian-10
-Nothing to download
-```
-
-This normally means you already have the template installed.
-It may be that you have the matching package installed, but you removed or renamed the template.
-Check `rpm -q qubes-template-<name>`.
-If it lists the package, but you don't really have the template present (`qvm-ls` doesn't list it), you need to clean up leftovers of the package with `rpm -e --noscripts qubes-template-<name>`, then install it normally.
 
 ### I keep getting "Failed to synchronize cache for repo" errors when trying to update my Fedora templates
 
-This is general Fedora issue, not a Qubes-specific issue.
+See [Update Troubleshooting](/doc/update-troubleshooting/#failed-to-synchronize-cache-for-repo-errors-when-updating-fedora-templates).
-Usually, this is due to network problems (especially if downloading updates over Tor) or problems with the download mirrors.
-Often, the problem can be resolved by trying again on a different connection (a different Tor circuit, if using Tor) or waiting and trying again later.
-Here are some examples of non-Qubes reports about this problem:
-
- - <https://ask.fedoraproject.org/en/question/88086/error-failed-to-synchronize-cache-for-repo-fedora/>
- - <https://unix.stackexchange.com/questions/390805/repos-not-working-on-fedora-error-failed-to-synchronize-cache-for-repo-update>
- - <https://www.reddit.com/r/Fedora/comments/74nldq/fedora_26_dnf_error_failed_to_synchronize_cache/>
- - <https://bugzilla.redhat.com/show_bug.cgi?id=1494178>
- - <https://stackoverflow.com/questions/45318256/error-failed-to-synchronize-cache-for-repo-updates>
-
-More examples can be found by searching for "Failed to synchronize cache for repo" (with quotation marks) on your preferred search engine.
 
 ### I see a "Failed to start Load Kernel Modules" message on boot
 

user/troubleshooting/update-troubleshooting.md

@@ -0,0 +1,51 @@
+---
+layout: doc
+title: Update Troubleshooting
+permalink: /doc/update-troubleshooting/
+---
+
+# Fixing issues that arise during updating #
+
+
+
+## “Failed to synchronize cache for repo” errors when updating Fedora templates ##
+
+This is general Fedora issue, not a Qubes-specific issue.
+Usually, this is due to network problems (especially if downloading updates over Tor) or problems with the download mirrors.
+Often, the problem can be resolved by trying again on a different connection (a different Tor circuit, if using Tor) or waiting and trying again later.
+Here are some examples of non-Qubes reports about this problem:
+
+ - <https://ask.fedoraproject.org/en/question/88086/error-failed-to-synchronize-cache-for-repo-fedora/>
+ - <https://unix.stackexchange.com/questions/390805/repos-not-working-on-fedora-error-failed-to-synchronize-cache-for-repo-update>
+ - <https://www.reddit.com/r/Fedora/comments/74nldq/fedora_26_dnf_error_failed_to_synchronize_cache/>
+ - <https://bugzilla.redhat.com/show_bug.cgi?id=1494178>
+ - <https://stackoverflow.com/questions/45318256/error-failed-to-synchronize-cache-for-repo-updates>
+
+More examples can be found by searching for "Failed to synchronize cache for repo" (with quotation marks) on your preferred search engine.
+
+## Lost internet access after a TemplateVM update ##
+
+In earlier versions of Qubes, there were situations where qubes lost internet access after a TemplateVM update. The following fix should be applied in recent versions of Qubes. 
+
+Run `systemctl enable NetworkManager-dispatcher.service` in the TemplateVM upon which your NetVM is based. 
+You may have to reboot afterward for the change to take effect. 
+(Note: This is an upstream problem. See [this Redhat ticket](https://bugzilla.redhat.com/show_bug.cgi?id=974811)). 
+For details, see the qubes-users mailing list threads [here](https://groups.google.com/d/topic/qubes-users/xPLGsAJiDW4/discussion) and [here](https://groups.google.com/d/topic/qubes-users/uN9G8hjKrGI/discussion).)
+
+## Windows update is stuck ##
+
+This has nothing to do with Qubes. 
+It's a longstanding Windows bug.
+More information about this issue and solutions can be found [here](https://superuser.com/questions/951960/windows-7-sp1-windows-update-stuck-checking-for-updates).
+
+## Dom0 and/or TemplateVM update stalls when updating via the GUI tool
+
+This can usually be fixed by updating via the command line.
+
+In dom0, open a terminal and run `sudo qubes-dom0-update`.
+
+Depending on your operating system, open a terminal in the TemplateVMs and run:
+* Fedora: `sudo dnf upgrade`
+* Debian: `apt-get update && apt-get dist-upgrade`
+
+

user/troubleshooting/vm-troubleshooting.md

@@ -71,3 +71,20 @@ If you face this error when starting a VM, look into the VM logs at `/var/log/xe
 Common reasons that may be revealed are: too low memory, corrupted files or a VM crash on startup. 
 
 If the error occurs as a result of too little initial memory, increase the initial memory from 200MB to 400MB by navigating to VM settings » Advanced » Initial memory. 
+
+## "No match found" when trying to install a TemplateVM ##
+
+For example:
+
+```
+[user@dom0 ~]$ sudo qubes-dom0-update --enablerepo=qubes-templates-itl qubes-template-debian-10
+Using sys-whonix as UpdateVM to download updates for Dom0; this may take some time...
+No Match for argument qubes-template-debian-10
+Nothing to download
+```
+
+This normally means you already have the template installed.
+It may be that you have the matching package installed, but you removed or renamed the template.
+Check `rpm -q qubes-template-<name>`.
+If it lists the package, but you don't really have the template present (`qvm-ls` doesn't list it), you need to clean up leftovers of the package with `rpm -e --noscripts qubes-template-<name>`, then install it normally.
+