sgmcgee1967 Posted April 3 Posted April 3 Yesterday, I installed the 2.6.2 update. I am running Windows 11. When I opened Photo 2.6.2, I was greeted by 2.6.0 asking if I wanted to update to 2.6.2. I downloaded the MSI files again, not the MsiEXE. I ran the updates, and the updater told me that version 2.6.2. There was a launch button on the message. I clicked that, and Photo 2 started up to 2.6.2.3228. I hope you see if there is a fix for this. In the meantime, I'm returning to 2.6.0 until some of these issues are fixed. If you happen to have a solution, I would love to give that a try. Stephen PaulEC 1 Quote
Hilltop Posted April 3 Posted April 3 Can't you update in-program? In other words, let the apps do the updating? Quote
Paul Mudditt Posted April 3 Posted April 3 4 hours ago, sgmcgee1967 said: Yesterday, I installed the 2.6.2 update. I am running Windows 11. When I opened Photo 2.6.2, I was greeted by 2.6.0 asking if I wanted to update to 2.6.2. I downloaded the MSI files again, not the MsiEXE. I ran the updates, and the updater told me that version 2.6.2. There was a launch button on the message. I clicked that, and Photo 2 started up to 2.6.2.3228. I hope you see if there is a fix for this. In the meantime, I'm returning to 2.6.0 until some of these issues are fixed. If you happen to have a solution, I would love to give that a try. Stephen So you installed the V2.6.2 update and you correctly identified the V2.6.2 update (Full version number 2.6.2.3228) so I fail to see the problem? Check under Windows -> About and you will see app is V2.6.2. If you look under your account it will show the base version plus the extra minor build number added i.e. V2.6.2.3228.(This last digit increments internally in the software team as they come closer to customer release.) PaulEC 1 Quote Affinity Photo, Designer, Publisher 1.10 and 2.6 on macOS 15.4 Beta Sequoia on M1 Mac Mini 16GB 1TB Affinity Photo, Designer, Publisher 1.10 and 2.6 on Windows 10 Pro. (revived !) Affinity Photo, Designer, Publisher 2.6 on M1 iPad Pro 11” on iPadOS beta 18.4 Recommended Fan based Affinity Support Groups on Facebook https://www.facebook.com/groups/AffinityForiPad https://www.facebook.com/groups/AffinityPhoto/ https://www.facebook.com/groups/affinityphotoastrophotography The hardest link to find https://affinity.help Mud’s Macros Library:- https://forum.affinity.serif.com/index.php?/topic/156842-muds-macros-v11-library-content-aware-move-added/
walt.farrell Posted April 3 Posted April 3 On 4/3/2025 at 8:18 AM, sgmcgee1967 said: I downloaded the MSI files again, not the MsiEXE. Your choices are MSIX or MSI/EXE. If the application gave you an option to Download (rather than an option to Install), then you were running the MSI/EXE version, and that is the one you should download and install. I would uninstall the one you just installed, run the old 2.6.0 one, and this time when you Download choose the right version. This has tripped-up many users who choose to run the MSI/EXE version, but it is something each of them needs to remember to do for each new update. tzulah, HCl, Paul Mudditt and 1 other 3 1 Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.5, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.5
tzulah Posted April 18 Posted April 18 I just wanted to chime in to say this fix worked for me. I was frustrated that after this latest update, Designer kept opening in the old version. I would try to run the update again, and it would say "This is already installed. Do you want to launch it?" And I'd say Yes, and then it would open the correct version. But I couldn't for the life of me figure out how to set it to remember to always use that version, or how to get rid of the old one. Anyway, yep, turns out I had previously install the .exe for the last version, and this time I used the .msix. I got the new .exe and installed that, and everything's working as expected now. Thanks for the info Walt! Paul Mudditt 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.