[Activation on Windows 2019 Server]

THis happens more often than you think, I had it myself a few times...

[Activation on Windows 2019 Server]

Well, it is a "local" setup, meaning that the folder are not on a network drive.

okay, after removing the files under "common" it seems to work.

The good-ole-turn-off-turn-on-try-again seems to have worked...

[Activation on Windows 2019 Server]

here it is:

[2023-11-22T16:23:14.185+0100] Affinity Photo 2
[2023-11-22T16:23:14.186+0100] IsSandboxed: No
[2023-11-22T16:23:14.186+0100] AppDataPathForCurrentUser: C:\Users\crash\AppData\Roaming\Affinity\Photo\2.0
[2023-11-22T16:23:14.186+0100] AppDataPathForCurrentUserPersisted: C:\Users\crash\AppData\Roaming\Affinity\Photo\2.0
[2023-11-22T16:23:14.187+0100] AppDataPathForAllUsers: C:\ProgramData\Affinity\Photo\2.0
[2023-11-22T16:23:14.187+0100] CommonDataPathForCurrentUser: C:\Users\crash\AppData\Roaming\Affinity\Common\2.0
[2023-11-22T16:23:14.187+0100] CommonDataPathForCurrentUserPersisted: C:\Users\crash\AppData\Roaming\Affinity\Common\2.0
[2023-11-22T16:23:14.188+0100] CommonDataPathForCurrentUserPersistedBuildInvariant: C:\Users\crash\AppData\Roaming\Affinity\Common\2.0
[2023-11-22T16:23:14.188+0100] CommonDataPathForAllUsers: C:\ProgramData\Affinity\Common\2.0
[2023-11-22T16:23:14.189+0100] TempPathForCurrentUser: C:\Users\crash\AppData\Roaming\Affinity\Photo\2.0\temp
Begin check for updates...[DXGI] Enumerating adapters
Microsoft Basic Render Driver
    HardwareID: PCI\VEN_1414&DEV_008C&SUBSYS_00000000&REV_00
    LUID: 0x983C
Microsoft Basic Render Driver
    HardwareID: PCI\VEN_1414&DEV_008C&SUBSYS_00000000&REV_00
    LUID: 0x9780
[OpenCL] Found 1 platforms:
Name: Intel(R) OpenCL
    Vendor: Intel(R) Corporation
    Version: OpenCL 1.2
[2023-11-22T16:23:17.122+0100]     Installed
[2023-11-22T16:23:18.043+0100] ...check for updates completed
[2023-11-22T16:23:18.054+0100] No update is available.
[2023-11-22T16:23:26.725+0100] Wintab: Failed to load Wintab32.dll
[2023-11-22T16:23:26.725+0100] Wintab: Failed to create tablet context
[2023-11-22T16:23:26.727+0100] Content migration already offered previously

 

[Activation on Windows 2019 Server]

KVM/QEMU

[Activation on Windows 2019 Server]

Okay. when I do NOT select to import Version 1, it starts, however, it closes again after a few seconds.

One of the programs (publisher) does not have a connection to the account  and asks me for credentials (NOT the activation screen but the start screen). When I enter them it claims to have no internet connection.

 

designer 2.0.zip publisher 2.0.zip photo 2.0.zip

[Activation on Windows 2019 Server]

Please see the screenshots below.

When I rename the 2.0 folder and start an app the first time, I agree to the licenses and he asks me to import data from version 1. I say yes, the programm closes.

When I restart, the activation windows appears. I enter my ID -> "Please try again".

Connecrtivity Check -> See screenshot.

So, back to square one for me.

[Activation on Windows 2019 Server]

17763 is the most current build for Windows Server 2019

 

https://learn.microsoft.com/de-de/windows-server/get-started/windows-server-release-info

[Activation on Windows 2019 Server]

When I try the "Connectivity Test" it shows the popup but nothing happens (as user). The windows cannot be closed, only via Task Manager

However, when I use the links of the FAQ in a browser (as user), the pages load without problem.

The system is:

Windows Windows Server 2019 Standard, Version 10.0.17763 Build 17763

Now, one strange thing happens: When I start any app as Adminsitrator it loads, then I close it and quickly start the same app as user it also starts. If I start a different Affinity app, the activation screen pops up.

[Activation on Windows 2019 Server]

Actually it is not, as I use Windows Server for security and practial reasons (i.e. no forced updates) and prefer the Server versions to the "private".

As I am running linux on my main machine, I virtualize the Windows Host to be able to access a few selected Windows apps I need.

[Activation on Windows 2019 Server]

Hi

I installed all three Affinity Apps on Windows 2019 Server. I had to install them as Administrator. I can activate them as Administrator.

However, when I start them as User, I get "Please Try Again" each time I enter my credentials.

How can I make them usable for my user account?

Thank you.

[Installation of Affinity Photo 2 does not work]

das ist sehr unschön.

[Installation of Affinity Photo 2 does not work]

Windows 2019 Server Build 10.0.17763

 

[Installation of Affinity Photo 2 does not work]

Das gleiche Problem habe ich auch unter Windows 2019 Server. Der Store steht hier auch nicht zur Verfügung. Wie kann ich Die V2 installieren?

Ärgerlich das hier ein MSIX ohne ersichtlichen Grund verwendet wird, wo es ein MSI oder EXE sicher auch getan hätte (MSIX wurde ja erst mit Windows 11 eingeführt).

Und ärgerlich, dass ich natürlich sofort die V2 gekauft habe und jetzt feststellen muss, dass ich es gar nicht installieren kann.

Wie kann ich V2 installieren?

Danke.

[Save failed because the file could not be written to (split)]

Does not work on Windows either (no save on network drive). This is extremely annoying and *not* explainable by any excuse. There is no other program I have ever used that has a problem with saving files to a network share.

[Publisher Completely Unstable]

@hilltop: see my other post regarding being unable to update. Both are resolved after a reboot, see post above.

Thank you.

[Publisher Completely Unstable]

Well, well well. Again Microsoft played it's mastercard. After a restart, all instability is gone... Coming from Linux, restarts are just so... we'll I do not know, they do not make sense.

Sorry for stirring up the air here.

[Backup Settings]

Well, I typically sync my app-data folders (in the profile directory and program data) to a network drive just in case. So, I will check what I will need.

 

Thanks for the help.

 

[Backup Settings]

Hi

I am using Affinity on Windows Desktop and purchased it directly at Affinity (all of them). I will try backing up the app folders to see if I can do a disaster recovery.

 

Thank you

[Publisher Completely Unstable]

And I have none of the listed 3rd Party Software installed

[Publisher Completely Unstable]

Currently I am working with one. It is based on a flyer template I have used for other flyers with designer and there it worked well. It loads well and I can do bunch of other stuff with it - even using effects on layers. As soon as I click on the first layer, it crashes.

The file is rather large (80MB) and I'd rather not share it openly in the forum (1. it would be embarassing and 2. well it is a company file...).

I tried to copy it into designer - same problem.

Any ideas how to trace the problem? I could probably send it hidden, don't know how that works.

[Publisher Completely Unstable]

I just found when I tried to work with that file in Designer I have the same proble: As soon as I click on any layer, it freezes, too!

Designer is running on 1.7.2 (as there the update worked).

Help!Help!

[Publisher Completely Unstable]

Hi

I try to work with Publisher 1.7.1 however, it is practially impossible. As soon as I click on any layer it freezes completely. Reproducible. Also, after some manipulation of graphics, it freezes. I can save (as long as I do not touch the layers) the graphics, but immediately afterwards it freezes.

Help!

[Backup Settings]

Hi

I would like to back up my templates etc. of Affinity Software. What to I have to copy to make sure that I do not loose and template (e.g. raw templates) I made? And macros?

 

Thank you.

[Unable to Update Publisher (1.7.2)]

Hi

When I try to update Affinity Publisher with the current 1.7.2 version (downloaded twice to make sure that it is complete), I only get the message "Fehler beim Setup" (error in setup). No upgrade to 1.7.2 possible.

Any recommendation to work around this?

Thanks

[Cannot Safe Affinity Phone File on Network Drive]

I see from the other thread that it seems that only Affinity consideres it as "feature" while everybody else considers it as "bug". Well, I will go 100% with the "bug" one, as there are so many software (even under windows) that rely seriously on network access and they all work fine, that a rather simple graphics manipulation system of the Affinity* software not being able to handle it get very disturbing.

So I would really really really suggest to fix this bug.

I for myself for in a network centered environement with little or no local space, saving on netwrok drives is mandatory, not option.