Jump to content

Recommended Posts

Opened up the App this evening, and it said there was a new update available. I downloaded it and tried to install it. Got part way through, and I got "Update failed" message, and it left me with nothing. Tried it again using the exe file, and it failed again. Gone back to the previous version. Anyone else got problems with this update ?

Share this post


Link to post
Share on other sites

I get the same error.  Restart Windows and try again -- it works for me.


(12nov2019) Ryzen 1800x, Gigabyte AX370 K7, Samsung 970 EVO+ 1TB NVME-M.2 SSD, EVGA SuperNOVA 1000w G2 PS, Corsair Vengeance 64GB DDR4 3200 Mem, Logitech G910 KB, GeForce GTX 1080 Ti FTW3 441.12(12nov19), LG Ultra HD (2), Win 10 Pro x64, Affinity Photo/Designer/Publisher 1.7.3.481

Share this post


Link to post
Share on other sites

I tried rebooting, but this did not work either.

I also tried explicitly running as administrator from the right click menu.

In both cases, the installation fails.


Win 10 x64 1809. AMD Ryzen, 16GB RAM, 512GB NVMe SSD, nVidia GPU.

Share this post


Link to post
Share on other sites

Likewise 1.7.2.162 fails to to update.

Restarting Windows failed to cure the issue as installation failed again,

The existing version 145 was removed leaving only a shortcut.  I have reloaded 145 and it appears to works OK.

Using Windows 10

Share this post


Link to post
Share on other sites

On my box I have to uninstall the current beta version, restart the box, THEN install the newest beta.  This has been from the beginning of the beta testing for APub, though I never had this issue with the betas for AD or AP.  It's an inconvenience but works.

 

Share this post


Link to post
Share on other sites

Fotocat, that might indicate that this is Windows problem, and doesn't affect Macs. I'm on Windows 10.

MtnArch, I've been using Publisher since the first Beta, and I haven't had this problem before.

Anyone from Affinity going to comment ?

Share this post


Link to post
Share on other sites
11 minutes ago, Chrisw5 said:

Anyone from Affinity going to comment ?

This entire conversation has, I think, taken part on what is officially the weekend for the Serif staff. Your initial post was at 1:51pm EST on Friday, which is about 6pm at the Serif offices. That means that there are fewer staff members available to officially comment, and it's possible that those assigned weekend duty are busy with other threads or are not the appropriate people to be commenting on Publisher installation problems.

Have you tried restarting Windows?

Beyond that, if you open a command prompt window, and "cd" to the directory that contains the installation .exe file, you can generate a log of the install process which will show what went wrong. That might give you a hint of how to fix it, but if not it might help Serif. To get the log you would issue the following command (modifying the file name appropriately):

    affinity-publisher-public-beta.exe /log

The log file will be in the AffinitySetup directory in your Windows Temp folder.


-- Walt

Windows 10 Home, version 1909 (183623.476), 16GB memory, Intel Core i7-6700K @ 4.00Gz, GeForce GTX 970
Affinity Photo 1.7.3.481 and 1.8.0.514 Beta   / Affinity Designer 1.7.3.481 and 1.8.0.514 Beta  / Affinity Publisher 1.7.3.481 and 1.8.0.518 Beta

Share this post


Link to post
Share on other sites

The relevant part of the log, I think, is:

Quote

+Error: The cabinet file 'Main.cab' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.

That seems to indicate a corrupt download. However, if  it were corrupt I wouldn't expect it to be able to run at all. Have you tried disabling any anti-virus processing you may be running? Perhaps it's interfering with something.


-- Walt

Windows 10 Home, version 1909 (183623.476), 16GB memory, Intel Core i7-6700K @ 4.00Gz, GeForce GTX 970
Affinity Photo 1.7.3.481 and 1.8.0.514 Beta   / Affinity Designer 1.7.3.481 and 1.8.0.514 Beta  / Affinity Publisher 1.7.3.481 and 1.8.0.518 Beta

Share this post


Link to post
Share on other sites
13 hours ago, walt.farrell said:

Beyond that, if you open a command prompt window, and "cd" to the directory that contains the installation .exe file, you can generate a log of the install process which will show what went wrong. That might give you a hint of how to fix it, but if not it might help Serif. To get the log you would issue the following command (modifying the file name appropriately):

    affinity-publisher-public-beta.exe /log

The log file will be in the AffinitySetup directory in your Windows Temp folder.

Walt -

After I try to run the newest Beta file and get the "Setup Failed" message I tried to access this, and it does NOT exist on my box.  This happens on both my Win10-64 Pro desktop box as well as Win10-64 Pro laptop box.

As long as I uninstall first, reboot and install the most current beta (or try to update, then immediately reboot and install the latest beta) I don't run into any issues.  If I attempt to just upgrade/update it my boxes will ALWAYS fail.

 

Share this post


Link to post
Share on other sites
17 hours ago, walt.farrell said:

This entire conversation has, I think, taken part on what is officially the weekend for the Serif staff. Your initial post was at 1:51pm EST on Friday, which is about 6pm at the Serif offices. That means that there are fewer staff members available to officially comment, and it's possible that those assigned weekend duty are busy with other threads or are not the appropriate people to be commenting on Publisher installation problems.

Have you tried restarting Windows?

Beyond that, if you open a command prompt window, and "cd" to the directory that contains the installation .exe file, you can generate a log of the install process which will show what went wrong. That might give you a hint of how to fix it, but if not it might help Serif. To get the log you would issue the following command (modifying the file name appropriately):

    affinity-publisher-public-beta.exe /log

The log file will be in the AffinitySetup directory in your Windows Temp folder.

I tried to do what you suggested, but my installer is actually called

affinity-publisher-beta-1.7.0.162.exe

And when I try to use the command option /log, I get a popup dialog titled "Affinity Publisher Setup", with two options /help and /extract. There is no log option and it only displays that dialog box, then the installer terminates.


Win 10 x64 1809. AMD Ryzen, 16GB RAM, 512GB NVMe SSD, nVidia GPU.

Share this post


Link to post
Share on other sites

From some other posts I've seen from the Serif staff, creating the look may be automatic for Publisher. So, try running the installer normally and then looking for the setup logs in the Affinity setup folder in you Windows Temp folder.


-- Walt

Windows 10 Home, version 1909 (183623.476), 16GB memory, Intel Core i7-6700K @ 4.00Gz, GeForce GTX 970
Affinity Photo 1.7.3.481 and 1.8.0.514 Beta   / Affinity Designer 1.7.3.481 and 1.8.0.514 Beta  / Affinity Publisher 1.7.3.481 and 1.8.0.518 Beta

Share this post


Link to post
Share on other sites
22 minutes ago, walt.farrell said:

From some other posts I've seen from the Serif staff, creating the look may be automatic for Publisher. So, try running the installer normally and then looking for the setup logs in the Affinity setup folder in you Windows Temp folder.

Thanks for the suggestion, I did find the log files in a folder under AppData...

C:\Users\UserName\AppData\Local\Temp\AffinitySetup\419bcc15-e67e-11e8-87ad-6045cb9fb899

Also, there were entries in the Event Log, which indicated as suggested yesterday, that the installer is corrupted. I downloaded the installer twice, they both do the same thing. Both were "affinity-publisher-beta-1.7.0.162.exe" with the version number attached. Neither behave differently, i.e. both fail to install the same way.

The first error in the Event Log was:

Product: Affinity Publisher Public Beta -- Error 1335. The cabinet file 'Main.cab' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.

I can post the SetupUi.log file, but I doubt it will tell you much more, other than the exact config of my machine.

Any further thoughts are appreciated.


Win 10 x64 1809. AMD Ryzen, 16GB RAM, 512GB NVMe SSD, nVidia GPU.

Share this post


Link to post
Share on other sites

Weekend over, and Affinity have responded. I sent them the Setup log, and they asked me to send them a copy of the .exe file, which I've done. Wait and see if they find anything.

Share this post


Link to post
Share on other sites

It seems that there is something wrong with the download, I imagine, that it will be corrupted at one of the CDNs.


Win 10 x64 1809. AMD Ryzen, 16GB RAM, 512GB NVMe SSD, nVidia GPU.

Share this post


Link to post
Share on other sites

Affinity replied, saying that the Security Certificate was corrupt. They sent me a new .exe file via Dropbox, which worked perfectly - so my problem, at least, is solved.

Many thanks to all of you for your input.

Share this post


Link to post
Share on other sites

Hi Chris,

The file you published did work for me, it just installed as would be expected, so it looks like that was (at least from my perspective) the problem.

Thanks.

K


Win 10 x64 1809. AMD Ryzen, 16GB RAM, 512GB NVMe SSD, nVidia GPU.

Share this post


Link to post
Share on other sites

There is a new version of the software, which fixes a bug, and seems to install correctly.

That probably means that this is now resolved, as there is a later version you are better off installing.

 


Win 10 x64 1809. AMD Ryzen, 16GB RAM, 512GB NVMe SSD, nVidia GPU.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.