Leigh
-
Posts
3,231 -
Joined
Everything posted by Leigh
-
Ok, thanks for trying. What's strange is that Microsoft Desktop App Installer would have been used to install V2. According to this thread on SuperUser someone had the same issue but using Powershell fixed it. What version of Windows are you on? -
It will actually be called App Installer in Task Manager. Can you try Terminating this process and try again?
-
Thanks for trying. Can you try restarting your machine and try again? if that fails, can you go into EventViewer and see if you have anything listed there relating to this issue: Application and Services Logs > Microsoft > Windows > AppxDeployment-Server > Microsoft-Windows-AppXDeploymentServer/Operational
-
Hope this helps!
-
Sorry to hear that you're having issues. Can you try opening PowerShell as an Admin and run the following command: Add-AppxPackage -Path "https://aka.ms/Microsoft.VCLibs.x64.14.00.Desktop.appx" Let me know how you get on.
-
If you're getting the error App Installer failed to install package dependencies. Ask the developer for package when installing Affinity V2 on Windows, you will need to download and install the Microsoft.VCLibs.x64.14.00.Desktop.appx package from Microsoft here. Once installed you will be able to install Affinity V2 without any issues.
-
That's great to hear - thanks for letting me know.
-
Can you download and install Microsoft.VCLibs.x64.14.00.Desktop.appx from here and then try reinstalling V2 again. Let me know how you get on 👍
-
If you're trying to install the Affinity Store or Microsoft Store version of Affinity on Windows and it's failing with the following reason: Windows cannot install package ... because the package requires architecture x64, but this computer has architecture x86. (0x80073d10) This indicates that your machine doesn't have a 64 bit CPU. Our apps require a 64 bit CPU to install and run.
-
If you're trying to install the Affinity Store or Microsoft Store version of Affinity on Windows and it's failing with the following reason: Windows cannot install package ... because this package is not compatible with the device. The package requires OS version 10.0.19041.0 or higher on the Windows.Desktop device family. The device is currently running OS version 10.0.xxxxx.xxx. (0x80073cfd) This indicates that your version of Windows is not supported. Our apps require Windows 11 or Windows 10 May 2020 Update (2004, 20H1, build 19041) or later to install.
-
We're aware of the below issues that occur when you have Pencil Hover enabled on a iPad Pro M2: Groups cannot be expanded in Layers menu via double tap Cannot add nodes to a curve Cannot select an object in a group using Move tool Selecting an object with Move tool, moves the object slightly This is currently logged with our developers.
-
Whether you want to learn the basics or want to master the apps, check out the Learn Section on our website: https://affinity.serif.com/learn/
-
- 2
-
-
- v2
- learning resources
- (and 4 more)
-
With Affinity V2 now available, we’ve put together a list of FAQs that will hopefully answer any questions you have: https://affinity.serif.com/affinity-2-faq/ For more information on the Affinity V2 licence and registration process, please read the following guide: https://affinity.serif.com/learn/in-app-licence-activation/
-
We're aware of an issue with Affinity V2 apps on macOS Ventura where the Brush Cursor will disappear in-between brush strokes or upon selection of a brush tool. A workaround is to simply zoom in and out to get the cursor back but we hope to fix this issue in a future update.
-
How do I update Affinity V2 apps?
Leigh replied to Leigh's topic in Frequently Asked Questions about V2 software
If you purchased you're Affinity app through the Affinity Store it's possible to download the latest and previous versions directly from our website. Please read the following FAQ: -
To find out how to download the latest version of our apps from the App Store, Mac App Store and Windows Store, please read the below FAQ:
-
Pantone Support
Leigh replied to Sam Neil's topic in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)
We're not changing anything and our apps will continue to include Pantone colours. -
Unfortunately we don't currently officially support Stage Manager on iPad or macOS with the Affinity apps, our apologies. Our team are aware of issues when using this feature (such as slow 'switching' between apps on macOS, occasional crashing when switching apps and lack of full screen external monitor support on iPad) and we're working to hopefully address these issues in a future update.
-
If you've updated to macOS Ventura you could be having this issue:
-
No. To use StudioLink in Affinity Publisher V2 you will need to have Affinity Designer V2 and Photo V2 installed.
-
Unfortunately, we're aware of an issue affecting users on macOS Ventura when trying to save to an external drive such as a flash drive that has a FAT partition. You will be able to initially save to the flash drive as expected but any subsequent saves to the same file will give the error: "Failed to save document. Save failed because access to the file was lost. The document must now be closed." This issue is logged with our developers for further investigation but saving locally and to a non FAT partitions is unaffected.
-
After updating your iPad to iPadOS 16 you will find that it's no longer possible to print from any Affinity iPad apps. Our developers are aware of this issue but a workaround is to go to Document > Export > Share > Print.
-
I don't have much more information to share at the moment, sorry. When I do, I will let everyone know.
-
As usual @lacerto, your help is very much appreciated. We don't recommend this workaround but I don't see why users can't be given this information so that they can make their own decision on how to get around this issue and get their apps working again. I've added a link to your workaround in this FAQ with a disclaimer - hope you don't mind.
-
To confirm, this issue has been logged with our developers and the developers at Microsoft. These KB updates from Windows are related to .NET and have also affected other .NET apps too. When we get more information from our developers or Microsoft regarding this issue, we'll let everyone know. There’s an unofficial workaround that our developers are aware of but it’s not something they recommend as it may cause unforeseen issues with the app. However, @lacertohas also provided this information for users wanting to go this route instead of removing updates - it can be found here. Again, Serif do not recommend this option and it’s not something we can support should anything happen with the app with this workaround enabled.
