A point release is not a separate, new version of Whonix. Instead, it is a re-release of Whonix which is inclusive of all updates up to a certain point.
Installing any version of Whonix 14 and fully updating it leads to a system which is identical to installing a Whonix point release.
If the Whonix installation is updated, no further action is required.
Regardless of the current installed version of Whonix, if users wish to install (or reinstall) Whonix for any reason, then the point release is a convenient and more secure method, since it bundles all Whonix updates that are available at that specific time.
I said the magic words, and then Jinny appeared and told me “Tell your friend 0brand that his magic words are outdated and he need to renew his payment to update his magic words”.
I wonder why a system restart is required. Really should not. Perhaps UpdateVM restart is enough since that would clear the root image of the VM. But then this would still be a Qubes bug.
I can’t remember exactly where is saw this but I know in the past users have had to restart their system to install new TemplateVMs. Definitely a Qubes bug. I’ll see if i can find an example or two in qubes-users or qubes-issues.
No luck finding previous reports on this i.e. users reports Qubes restart fixes the issue. I saw them somewhere… Even so, it might not actually be “Qubes restart”. It could be as Patrick suggested, an UpdateVM restart that actually fixes the issues. Its difficult to tell since we don’t have steps to reproduce – command run, error output… – you know, stuff an experienced Whonix team member would provide
It looks like similar issues have been reported in qubes-issues but they were UX issues (resolved), bugs (resolved), user errors etc. So no point in list the links.