|
|
Post by michelb on May 5, 2018 19:16:53 GMT
I think it will be ok to post this in the Elements editor section. From discussions on the Adobe Forums it appears that the April update of Windows 1 which will be installed in the next weeks does not create serious problem with most Adobe softwares... but that may not be so with Elements. forums.adobe.com/thread/2486258forums.adobe.com/thread/2423579forums.adobe.com/thread/2487356It's too soon to predict if this will hit a lot of Elements users (I am not in a hurry to test it myself  ). Those memory problems seem to happen with configs with a lot of RAM. It may be prudent to keep an eye on the feedback about those issues in the next days. If individual users have been able to find a solution by editing the registry (dangerous), I hope Adobe and/or Microsoft will solve the problem. (Your comments will be appreciated.) |
|
|
|
Post by Sepiana on May 5, 2018 20:04:07 GMT
Michel,
Thanks so much for bringing up this issue to our attention! As a matter of fact, the Windows 10 v.1803 update is being installed on my second computer right now. I do have several versions of Elements running on Windows 10 (7, 10, 11, 12, 13, 14, 15, 2018). I will start by checking Elements 2018 and will post the results here. Would you like me to check the other versions as well?
|
|
|
|
Post by michelb on May 5, 2018 20:26:43 GMT
Thanks very much, Sepiana.
Those posts mentioned versions 2018 and 2015. I don't expect significant differences between versions.
Of course, we only read posts by users having issues, maybe a lot of other users don't have them.
I hope we'll have better feedback from users with that recent Windows update. Specifying your main hardware specs may be useful.
|
|
|
|
Post by Sepiana on May 5, 2018 20:37:35 GMT
Michel,
You are most welcome! I will concentrate on checking those two versions of Elements. I will make sure to specify my computer hardware specs when I post back. Hopefully I will be the bearer of good news. Wish me good luck!  |
|
|
|
Post by Sepiana on May 12, 2018 4:10:11 GMT
Michel,
Here are my findings concerning the performance of PSE 2018 and PSE 15 after the installation of the Windows 10 v.1803 update. I focused my testing on the problems reported on the Adobe Forums. I used 5 randomly selected files, different sizes, pixel dimensions and formats (RAW, TIFF, PSD, JPEG, PNG).
Computer Specs:
Windows 10 Pro 64-bit Version 1803
Processor -- 7th Generation Intel Core (i7)
RAM -- 16 GB
Storage -- 1 TB
Graphics card -- Intel HD
Display resolution -- 2736 x 1824
Touch support with 10 touch points
PSE 2018 and PSE 15 Preferences:
Both versions allowed to use the default RAM amount (70%).
UI Scale Factor set to Large (200%).
Use Graphics Processor for Adjusting Facial Features -- Enabled.
Results:
PSE 2018 – NO PROBLEM
PSE 15 – NO PROBLEM
PSE 2018 – NO PROBLEM
PSE 15 – NO PROBLEM
PSE 2018 – NO PROBLEM
PSE 15 – NO PROBLEMPSE 2018 – NO PROBLEM
PSE 15 – NO PROBLEM |
|
|
|
Post by Sepiana on May 13, 2018 0:23:45 GMT
Michel, I went ahead and did some more testing. This time I focused on features/tools which are memory-intensive such as the Recompose tool, Photomerge Panorama, etc. Both PSE 2018 and PSE 15 passed the test with flying colors. No error message about not enough memory! NO PROBLEM!
|
|
|
|
Post by michelb on May 16, 2018 14:41:49 GMT
I have the problem with 'floating documents' described elsewhere.
|
|
|
|
Post by Sepiana on May 16, 2018 15:09:53 GMT
I have the problem with 'floating documents' described elsewhere. Michel, I don't have "Allow Floating Documents in Expert Mode" turned on. I will turn it on and check the situation. I will post back with my findings. |
|
|
|
Post by Sepiana on May 16, 2018 18:33:19 GMT
I have the problem with 'floating documents' described elsewhere.
Michel, confirmed. I have the same problem in both PSE 2018 and PSE 15.
|
|
|
|
Post by michelb on May 16, 2018 18:49:14 GMT
I have the problem with 'floating documents' described elsewhere.
Michel, confirmed. I have the same problem in both PSE 2018 and PSE 15.
There are several posts about the issue, and to my knowledge, no working solution today. The feature to open documents in floating windows now means you have to: - move the 'poststamp' sized window - resize it
each time you open a file. I think I'll do it anyway because I can't work without the floating windows, but that also means I'll have to curse Microsoft and Adobe everytime I open a new file! Going back to PSE14 is not realistic for me.
|
|
|
|
Post by Sepiana on May 16, 2018 21:01:44 GMT
There are several posts about the issue, and to my knowledge, no working solution today. The feature to open documents in floating windows now means you have to: - move the 'poststamp' sized window - resize it
each time you open a file.
That's not good, Michel! Having to take all these extra steps? No solution?
As I said earlier, I keep "floating windows" turned off. As a matter of fact, the moment I finished the testing, I went to Preferences and turned this feature off. That's my way of handling this issue.
You, an ACP, cursing Adobe? That should be fun to watch.
|
|
|
|
Post by Lillias on May 18, 2018 12:40:50 GMT
There are several posts about the issue, and to my knowledge, no working solution today. The feature to open documents in floating windows now means you have to: - move the 'poststamp' sized window - resize it
each time you open a file. I think I'll do it anyway because I can't work without the floating windows, but that also means I'll have to curse Microsoft and Adobe everytime I open a new file! Going back to PSE14 is not realistic for me. My Desktop PC just updated today with the Windows 10 v.1803 update and I am experiencing the exact same problem with PSE 15 as described above. The original OS on this PC was Windows 7 and was upgraded to Win 10. Whether that affects things I'm not techy enough even to speculate. My laptop which came with Windows 10 has still to be offered the Windows 10 v.1803 update and I will wait until it is and see what happens with that. So far I haven't discovered anything else of note and hopefully that's the way it will stay. |
|
|
|
Post by Sepiana on May 18, 2018 13:47:47 GMT
Michel,
Yesterday I helped a friend of mine install this Windows 10 update on her computer. She has 32GB RAM and is using PSE 2018. I focused on testing the problem areas mentioned in those Adobe forum threads. CONFIRMED for all of them! Furthermore, she has the same problem you and I have with floating documents. These results seem to confirm that a high amount of RAM is playing a key role here.
Her computer came with Windows 8 Pro. She had it upgraded to Windows 10 Pro by a Microsoft tech at one of their local stores. I believe this happened sometime last summer.
|
|
|
|
Post by michelb on May 18, 2018 14:15:40 GMT
Michel,
Yesterday I helped a friend of mine install this Windows 10 update on her computer. She has 32GB RAM and is using PSE 2018. I focused on testing the problem areas mentioned in those Adobe forum threads. CONFIRMED for all of them! Furthermore, she has the same problem you and I have with floating documents. These results seem to confirm that a high amount of RAM is playing a key role here.
Her computer came with Windows 8 Pro. She had it upgraded to Windows 10 Pro by a Microsoft tech at one of their local stores. I believe this happened sometime last summer.
I am not surprised at all in this case. There had already been complaints before the last Windows build 1803 update. Always with high amount of RAM. There were also problems with Photoshop CC, which was acknowledged in the following paper:
I also have summarized the situation in one discussion in the feedback forum:
|
|
|
|
Post by Sepiana on May 18, 2018 14:26:14 GMT
There had already been complaints before the last Windows build 1803 update. Always with high amount of RAM. There were also problems with Photoshop CC, which was acknowledged in the following paper:
I spent a lot of time yesterday checking both Photoshop CC and Lightroom CC running on the computer with this Windows update. There were no problems whatsoever! I have only 16 GB of RAM though.
I have PSE 14 running on the computer with this update. Would you like me to check the situation? |
|
).
