Post by megapixel on Jun 14, 2024 13:46:27 GMT
Earlier this year I discovered that after upgrading to Elements 2024, I could no longer print from the editor (see my post from back in April). When attempting to print from the Editor, the program would 'freeze', and I would have to resort to the Task Manager to escape from the program.
During numerous email exchanges with Adobe's support team, and trying suggestions that they made, the problem was not resolved.. They believed that the problem was related to 'Permissions', and I left it with them to investigate.
Yesterday I received an email from them, with a list of changes to try. This I did, and 'Bingo' the problem was resolved., and I reported back to them accordingly. Given the list of changes, which I detail below, I said that the end user should not be required to make these changes, and that someone with no IT knowledge would struggle. The 'bottom line' is that the team who coded Elements 2024, created a problem, that did not exist in earlier versions of Elements.
I should add that the problem existed with a Windows 10 PC, and with a clean install on a brand new Windows 11 PC. Both PCs with an i7 processor, and 16Gb of RAM.
The root of the problem now appears to be one of 'Permissions'.
As 'Administrator' I had to set multiple 'Permissions' to 'Allow'.
This needed to be done in the following folders:-
C:/Program Files/Adobe
C:Program Files/Common Files/Adobe
C:/Program Files(x86)/Common Files/Adobe
C:/Program Data/Common Files/Adobe (Program Data is a hidden file, so enable hidden folders on the C drive)
Press Windows + R, type "%appdata%" in the 'Run dialogue box and press Enter. This will reveal another Adobe folder. Provide 'Permisions' for this as well.
Finally 'Restart' the system.
Imagine 'average Joe Public', upgrading the Elements 2024, and then be expected to make these modifications.
Elements 2024 is a great program, but it should have been released as a Beta version, to uncover any 'bugs' prior to marketing, or at least fully V&Vd before release.
During numerous email exchanges with Adobe's support team, and trying suggestions that they made, the problem was not resolved.. They believed that the problem was related to 'Permissions', and I left it with them to investigate.
Yesterday I received an email from them, with a list of changes to try. This I did, and 'Bingo' the problem was resolved., and I reported back to them accordingly. Given the list of changes, which I detail below, I said that the end user should not be required to make these changes, and that someone with no IT knowledge would struggle. The 'bottom line' is that the team who coded Elements 2024, created a problem, that did not exist in earlier versions of Elements.
I should add that the problem existed with a Windows 10 PC, and with a clean install on a brand new Windows 11 PC. Both PCs with an i7 processor, and 16Gb of RAM.
The root of the problem now appears to be one of 'Permissions'.
As 'Administrator' I had to set multiple 'Permissions' to 'Allow'.
This needed to be done in the following folders:-
C:/Program Files/Adobe
C:Program Files/Common Files/Adobe
C:/Program Files(x86)/Common Files/Adobe
C:/Program Data/Common Files/Adobe (Program Data is a hidden file, so enable hidden folders on the C drive)
Press Windows + R, type "%appdata%" in the 'Run dialogue box and press Enter. This will reveal another Adobe folder. Provide 'Permisions' for this as well.
Finally 'Restart' the system.
Imagine 'average Joe Public', upgrading the Elements 2024, and then be expected to make these modifications.
Elements 2024 is a great program, but it should have been released as a Beta version, to uncover any 'bugs' prior to marketing, or at least fully V&Vd before release.
