Kája

I am also very disappointed. Aside from the problems mentioned above.... I tried open my RAW file, but AP crashed and suprisingly - I see no way to open it again besides restarting computer (funny that the attempt to open it ends with a message recommending to reinstall the program).

I really don't see a reason to irrevocably change something that worked well. Especially if you get paid for it.

Then the IT department of the parent company says no. They do upgrades across tens of thousands of machines across the world. If something goes wrong, people can literally die in our industry. They're not going to care that some users can't use this software. The software works on those versions of Windows, it's just the installer that doesn't. It was not a smart decision for Affinity to exclude users like this over an installer...

Pros:
MSI had an installation success rate of ~85% (and we have many requests to our tech support team for v1 install failures). MSIX promises a 99.9% success rate.  MSI requires admin privileges to install. MSIX installs per-user, but files are deduplicated so that disk space isn't wasted. MSI apps are not sandboxed from other applications, meaning other applications can break those apps (we have seen this with several third-party apps in the past). MSIX apps are sandboxed to prevent this. MSI updates require a manual download of the full ~550mb installer which must be manually installed. MSIX can perform in-app delta updates which are smaller and faster. MSI updates can only be performed one at a time. MSIX can update all three apps simultaneously. MSI cannot guarantee that an uninstall will leave your machine in the exact state prior to install. MSIX installs are segregated and don't rely on the registry or special filesystem locations meaning an uninstall always leaves you in a clean state. Installation and app data paths are cleaned on uninstall. MSI apps cannot integrate with Microsoft Photos app to provide "Edit In..." style features. MSIX can. MSI does not require a digital signature. MSIX does (this means any MSIX that appears to be from Serif, will be guaranteed to be from us and only us). Cons:
MSI can allow the user to change the installation directory. MSIX can move installed apps to different drives, but it cannot choose a specific directory (due to the sandbox). See below: MSI can allow an option to install a desktop shortcut. MSIX doesn't provide this as an option, but you can pin the apps to either the Start Menu or the Taskbar. There is also the secret Shell:AppsFolder location in Explorer that allows you to right-click or drag the icon to your Desktop for a shortcut as a workaround if you need it.  MSI has easy discovery of undocumented app locations for launching from a third-party. MSIX hides the install location due to the sandbox, but we use App Execution Alias to enable this scenario. You can find the aliases in the following location: C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityDesigner2.exe
C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe
C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPublisher2.exe
Remembering to replace username with your Windows username. Also, those paths are already in your %PATH% variable so you can often launch them without even specifying the full path, e.g. just AffinityPhoto2.exe. There are bugs in some third-party applications with the App Execution Alias , and the next post includes aflaunch.exe as a work around if you need that instead. 
 

Lee, 
the whole point of using Windows is not to have to put more effort into installing a program than will be needed to actually use the thing.
If we wanted to tool around with fixes, workarounds, additional downloads, troubleshooting and such nonsense, we'd be Linux users.
For myself I'm 100% compliant with the system requirements; I've tried every published workaround (and more besides); and I still can't get past the splash screen. 
There are umpteen posts on the forum decrying Serif's decision to fix something that wasn't broken by using MSIX - it's time that Serif took the hint and went back to an installation approach that just works.
 

THIS is the WORST DECISION from SERIF.
They claim you have the best software. BUT INSTALL HERE NO OTHER CHOICE.
NO HAPPY WITH THEM.
Bring back the OLD INSTALLER. My IT DEPT are wiping SERIF software from the network. YOU NEED A CHOICE. IT dept wont put up with this.
Gary
 

I've been told by IT support that our enterprise systems will not support MSIX any time in the near future.

As a result this software is useless to me where I need to use it most.

Will there be an exe/msi installer added or should I just refund it?

What's the deadline on getting a refund? I don't want to request a refund and then find in a month they provide an installer I can use and the sale is already over.

If I know there will be an alternative installer, I'm happy to keep using v1 until then. If one's not coming, I don't want to have wasted $100 USD that I can only use at home in my personal hours.
I don't know that to choose, I need answers. If there's no answer, can we get an extended refund period until it has been decided so we can make an informed decision?

Just bought the Suite and could not find the installation files so was unable to create shortcuts and worse unable to find a way to run the software! The only way I could launch the software was to double-click on the downloaded installation files which gave me the option to Launch from there. Total irritation and confusion.
However in the meantime after much faffing about through the Forum I discovered to my dismay that these are "App" files and do not install into the Program folder of my C drive and do not appear in my Programs & Features... How do I uninstall them?
I absolutely hate this unexplained change to installing/removing software and am not happy with the way this has been implemented, particularly as no advanced notification (as far as I could tell) was given.
I very much like what Serif is doing with Affinity and love the software but cannot stand this insane change to the standard installation procedure.
Please Serif fix this unwanted installation mess asap. and please retain some independence from the dumbing-down that Micro$oft continually applies to Windows in the so-called attempt to make it better.
I sincerely hope you listen.

So, 
I posted elsewhere the problems with new installer . The SO CALLED option to install to another drive is terrible. Look that  the MESS of a directory it creates
It is important for a lot of COMPANIES and WORKFLOWS to have correct directory structures. The inability to INSTALL the APPS where you want is a massive problem for a lot of us in the GRAPHIC DESIGN world ( particularly in FILM ).
I create graphics for movies and CONTRACT to many companies. I have had two notices this morning to stop using AFFINITY file formats and migrate to AI and EPS only. This is due to the NEW INSTALLER and they do not want to USE V2 because of it. Many of the companies and scripts and backups and a very strict workflow based on where things are and was the reason i was given.
I just got away from finally use of ADOBE software. Now i have to start a SUBSCRIPTION again.
This is a two fold issue in my case. FIRST off, I now need to spend more more money and go back to ADOBE . Two the companies are not PURCHASING V2 of AFFINITY Software ( one of the companies alone has 35 seats of the software ) .So now I have to output money for ADOBE and AFFINITY if i wish to keep using it. 
I love AFFINITY Software. Never had any complaints about what they have done or where they are going.
BUT THIS IS A BIG SCREW UP in my eyes. We DON'T use ANY software that doesn't allow us a choice on where to INSTALL.
 
PLEASE SERIF for those  that are reading this and listening, Please give us the choice of the old installer and keep the users.
 
Hope to hear something soon.
Gary
 

Click the thumbnail (not the name) of the nested object named "Background" to select only it and then do Layer > Rasterise To Mask.

Thanks for your document
I can confirm I have replicated this issue here and it is present when either Printing to PDF or Printing directly. It appears to be a conversion issue between the embedded CMYK document to your 'master' sRGB document.
I will log this with our developers as a bug, in the meantime if you select your Embedded document, then click Edit Document on the context toolbar. Now, with your Embedded document in view, go to File>Document Setup and select the Colour tab. Here, change the Colour Format from CMYK to RGB/8 and make sure the sRGB profile is in use. Press OK and now try printing your document to PDF, you should find this 'prints' correctly - I hope this helps!