Copy link to clipboard
Copied
I am unable to print from the Editor in Elements 2024, but I can print from the Organiser. I had the same issue with Elements 2023, and was hoping that the problem woud have been sorted in the 2024 version, but sadly not it would seem. I am running Windows 10 64 bit on a i7 based PC, with 16Gb of RAM
Copy link to clipboard
Copied
Hi Michel, thank you for your input. I will give that a try, but first I will backup all Files & Folders to an external drive. I had another emil from Adobe saying that they will get a senior technician to call me on Moday morning.
Copy link to clipboard
Copied
And so the saga continues!!. Ok Michel, having backed up the PC to an external drive, as a safety measure, I uninstalled Elements 2024, while electing not to delete preferences etc. Then to my Adobe account, dowloaded a fresh copy of Elements 2024, and installed it. As you said, my catalogue and albums had been retained. So far so good, NOT!!, the problem of being unable to print from the Editor remained. Do I rergret ever upgrading from version 2020, absolutely!!. With all of the upgrades I have made since the early version of Elements, I never experienced a problem, until now. Nothing has changed PC wise, except for Windows updates.
Copy link to clipboard
Copied
Well I guess I have come to the end of the road as far as printing from Elements 2024 Editor is concerned. It would appear that Adobe's support team have run out of ideas, and the promised call from a senior member of the support team, never materialised. Here's a summary of what I have informed Adobe:-
Copy link to clipboard
Copied
@daves92989679, thanks for reporting back. But you said: Uninstalled Elements 2024, electing not to delete preferences etc, in or order to retain my catalogue and album data. Deleting preferences does not remove any of your catalogue and album data. I just want to make sure that this is one of the options you have tried, as it normally fixes this kind of problem. If you havn't done so already, go to the Edit>Preferences>General tab and click the Reset Preferences on next launch button.
And as one final suggestion, uninstall the program and use the Creative Cloud Cleaner tool to remove all traces of Elements 2024 from your machine. (This will not affect your catalogue.) See my instructions in this post to walk you through the process for Elements.
Copy link to clipboard
Copied
Ok, Greg will try that tomorrow as its 23.30 here. I did try your first suggestion two or three times, but problem remained the same. I haven't uninstalled the Creative Cloud Cleaner Tool, but I will do, and report back. I don't use Adobe Cloud, as I much prefer to backup locally on external drives. Off to bed now 🙂
Copy link to clipboard
Copied
Good morning Greg. Ok, I uninstallled Elements 2024 including preference etc, downloaded and ran the Creative Cloud Cleaner. Also ran the Log Collector. No reference to Elements (any version) was displayed but I selected "all" that was there, and ran the cleaner. Reinstalled Elements 2024, but the inability to print from the Editor remained.
Copy link to clipboard
Copied
I am beginning to wonder if there is a compatiblity issue between Elements 2024 and Windows 10. As an experiment I installed Elements 2024 on my i5 based laptop which is running Windows 11, and the program worked fine. When as anoher experiment I installed an early version of Elements on the Window 10 desktop, that worked fine too. Ungfortunatley my destop PC is not compatible with Windows 11.
Copy link to clipboard
Copied
According to Adobe's published data, OS Build version of vesions of Windows 10 19044.3570 should be compatible with later versions of Elements. The build version on my PC is 19045.4291, so theoretially it should be ok?
Copy link to clipboard
Copied
I have decided to "bite the bullet", and buy a new PC. My Lenovo desktop top PC, although well specd, is quite few year old now, and not upgradable to Windows 11. Sooner or later it will probably fail, so probably time to move on. New PC on order with a 1TB ssd, 16GB of RAM, and a DVD writer which is a bit of a rareity now.
Copy link to clipboard
Copied
Good luck with the new computer. Yes, one with a DVD writer must be hard to find. 😊
Copy link to clipboard
Copied
Success!!. The new PC arrived, and commssioned. Elements 2024 loaded, and I can now print again from the Editor. I bought a 1TB M2 SSD, and installed it as second drive, where as with the old PC (SSD C Drive and HDD E Drive) I will store my images, and videos etc. Just need to load all Gigabytes of Programs, and data from the old PC. which will take some time.
Copy link to clipboard
Copied
@daves92989679, thanks for reporting back. Glad it is now working for you.
Copy link to clipboard
Copied
Interesting!!. When printing from the Editor, it will now print, but takes an age to start prtinting. If I print from the Organiser, it prints pretty much straight away. This is irrespective whether connected via wi-fi or usb. Brand new hi-spec PC, and a clean install of Elements 2024. As I understand it, the Organiser and Editor have different Print Engines. I can live with having to print from the Organser, but I will let Adobe Support know.
Copy link to clipboard
Copied
Interesting!!. When printing from the Editor, it will now print, but takes an age to start prtinting. If I print from the Organiser, it prints pretty much straight away. This is irrespective whether connected via wi-fi or usb. Brand new hi-spec PC, and a clean install of Elements 2024. As I understand it, the Organiser and Editor have different Print Engines. I can live with having to print from the Organser, but I will let Adobe Support know.
By @daves92989679
I don't think that the "different print engine" explanation makes sense, since I believe there is only one proprietary driver from the Printer supplier. That driver is accessed differently when printing orders come from the organizer or the editor, that's where Adobe must find the real handling difference. I have never met similar issues either from Win 10 or Win 11 on different computers.
I prefer printing from the organizer.
I don't use the printing software offered by the printer supplier, even if it is always more powerful and secure than printing from PSE. My view concerning printing choices such as margins is that I have to find what is best done by an image editor and what is made from a printing tool. For instance, that means that dealing wih size format, resolution, margins... is best done in Elements. So I take care to produce a "ready to print" version to send to the printer, even if I don't really need to save it in a version set. That's where using pre-defined templates may save a lot of time and thinking.
Copy link to clipboard
Copied
The different Print Engine theory is only from what I read somehere on the web. I have been using Elements since version 2012, and have upgraded several time since. Until now, had always printed trouble/delay free from the Editor. The problem appeared when I ugraded to version 2023. and has carried over into v2024. As I mentioned earlier, as a test, I reinstalled v2019, and I could print without problem, or delay, from the Editor, or the Organiser. This morning I ran off a couple of A4 photo prints, the first via the Editor, and I had time to make a cup of tea before it printed. The second one, I opted to print from the Organsiser, and it printed pretty much straight away. There is no doubt in my mind that something in the Editor's print function coding, changed in v2023 and 2024. I have informed Adobe Support. I the mean time I'll print from the Organiser, albeit not my personal preference.
Copy link to clipboard
Copied
Yes Dave, I have followed your posts on both forums. I am aware of your particular problems and I agree that Adobe must find what is different between the commands issued by the editor and the organizer.
From what I have read from this forum, the number of complaints is not important (most users don't complain), but significant enough to point to the need for investigation.
The first time I did see the theory of two differents engines was a post by @hatstead , which may be able to remember where he learnt that info.
On the other hand, I can understand the Elements team if they still cannot replicate your issue (like me). It's as important to find why some users have a given problem as finding the real difference of driver handling.
Copy link to clipboard
Copied
@MichelBParis, I don't think it is any secret that there are two different print engines. There are some subtle differences between the two. I don't think there has been any work on either of them since the earliest versions of the program. And since I supsect that most people share their images digitally, I would not expect Adobe to put any further effort into printing.
Copy link to clipboard
Copied
QUOTE: "I don't think there has been any work on either of them since the earliest versions of the program"
That may be so Greg, but at the time when I upgraded to v2023, there had been no changes, or additions to my PC, and yet the problem arose.. It was the reason I upgraded to v2024, other than that, there was nothing else in v2024 that I needed. In future if I upgrade, I will download the trial version first, and check it for 'Gremlins' before spending the money.
Copy link to clipboard
Copied
It is always a good idea to download the trial version to see if it meets your needs.
Copy link to clipboard
Copied
"Hindsight is a wondeful thing" (lol)
Copy link to clipboard
Copied
"wonderful" even. No provision to edit a post on the 'Board'
Copy link to clipboard
Copied
I was having the same issue of not being able to print from Adobe Elements 2024 Editor. I found a solution that appears to work. Try holding the spacebar while clicking "print". Apparently this removes all old print metadata embedded in the file.
Copy link to clipboard
Copied
Hi Steve. The problem was evenually solved by the Adobe Support Team, who traced it to one of "Permission", which after making several changes to the Elements program files, cleared the problem. The problem was clearly created by the coding team, as it did not exist in earlier versions. Hopefully it will be corrected in future versions