@grafxgalkc  You need to explain this. Show screenshots as the file appears in Windows Explorer, and any error messages you get.   Do you have file extensions visible in Windows? Some laptops come with extensions hidden by default, which is a very bad idea causing double extensions/missing extensions/all kinds of problems. ... View more

DirectX 12 is a set of APIs, application programming interfaces. Your GPU supports that.   DirectX feature level is something else. It's a measure of the GPU's actual capabilities, what it can do.   In other words, while your GPU "speaks the language", it cannot actually execute all the required functions. ... View more

I think you're overcomplicating this. Essentially, you're trying to impose color management on applications that don't support color management.   Just a quick rundown on how color management works, when the application supports it: The monitor profile describes the measured behavior of the monitor, in its current and actual (calibrated) state. An icc profile is a description of a color space. It doesn't do anything; it's just a map. But like any map, it needs to correspond to the actual terrain. This profile is used in a standard profile conversion, from the document profile and into the monitor profile. This conversion is performed by the application, on the fly, as you work. The corrected numbers are sent to screen. Photoshop loads the monitor profile it gets from the operating system at application startup. This profile is used for the remainder of the session. If the default profile is changed in the operating system, the application needs to be relaunched to pick that up.   Color management in Windows isn't difficult, and you can use wide gamut monitors without any problems. I've done that for more than fifteen years. All you need to do, is use applications that actually support color management.   Yes, there are slight complications like the fact that the actual profile conversion is executed in the GPU, so that needs to work without problems. And HDR monitors are an obvious paradigm shift that changes a lot of rules. For the moment, Photoshop doesn't support HDR in Windows, so that's moot (but ACR and Lightroom do).   ... View more

@ExUSA  AI per se is not a problem. Generative AI - i.e. Firely - is a problem. Noise reduction is fine. Generating new content is not fine. That's where you're crossing the line.   It is in fact extremely easy to avoid crossing that line: just don't accept the terms and conditions for Firefly. If you're picking up a tool that uses Firefly, you need to accept the terms before you can use it.   I have never accepted the terms, and for those tools that can go both ways, like the Remove tool, there will be a rolldown in the options bar: Once that is set, you won't be bothered again. ... View more

That sounds very risky, and this is certainly not a supported procedure. I'd say it's asking for trouble. Save locally, then copy over.   End whatever's still running in Windows Task Manager, even if it means losing your work. Then reboot and start again.   https://helpx.adobe.com/ca/photoshop/kb/networks-removable-media-photoshop.html  ... View more

But you can still tell us where you're saving to. ... View more

No problem. Good luck 🙂 ... View more

I’ve been using Photoshop for years By @David_Hennry3382   Did you use Photoshop in 2010, CS4 and earlier?   Then you may remember that saving to jpeg was not possible at all, if you had a 16 bit/layered file. You had to flatten and convert to 8 bit first.   Directly saving out a jpeg copy from 16 bit/layered files was introduced in CS5 in 2010, with much fanfare. ... View more

Well, first we need to see it. @SSL-ADT , please post a screenshot, showing the full Photoshop interface with the image. ... View more

Original document (of course in your case it should read sRGB IEC61966-2.1):   PDF: ... View more

OK, that's weird. Can you post the full Help > System Info from Photoshop? ... View more

Are you saving directly to external storage and/or over a network connection?   Both are officially unsupported and increase corruption risk by orders of magnitude. Save locally, then copy over. https://helpx.adobe.com/ca/photoshop/kb/networks-removable-media-photoshop.html  ... View more

That's your choice. Adobe's user base exploded after they introduced the subscription model - probably because the prohibiting entrance threshold vanished and it was suddenly something everybody could afford. It doubled or tripled in a few years.   Perpetual licenses aren't really perpetual. Sooner or later they stop working, because operating systems change and hardware changes. So you need to purchase upgrades to stay in the game. You need to factor that into the equation. Photoshop CS6 still barely works on Windows, with significant issues, but on Mac CS6 has been useless for a long time.     ... View more

Does your original file have the sRGB profile embedded? Is that profile still embedded in the PDF? ... View more

Try to uninstall/reinstall first. That usually fixes it.   Going into the registry is last resort and rarely necessary. If you need to do that, search for updated info first.   And to avoid the whole problem in the future, uninstall the old version first, then install the new version. Always follow version order both ways. Think of it as tennis ball in a plastic tube, open only at the top. ... View more

OK, a couple more things:    One, your memory allocation in PS preferences is far too high at 94%. That will choke the rest of your system. Set it back to 70% maximum. Other processes need memory too! This is mainly handled by the scratch disk, not RAM (you're getting low on scratch disk space too, but not yet critical).   Reset preferences by moving the whole folder out of your user account so a new can be built. Preferences contain the whole application configuration, not just your own user settings.   A few checkboxes to try:   Uncheck GPU compositing Uncheck OpenCL in the GPU settings. OpenCL is being phased out and not used much anymore. Check "older GPUs" in PS preferences > Technology previews.   ... View more

Yes, dual graphics is a known problem. Disable the Intel UHD. See section 6 & 7 here: https://helpx.adobe.com/photoshop/kb/troubleshoot-gpu-graphics-card.html    ... View more

Then the question is why it keeps crashing. Please post the full Help > System Info. ... View more

OK. Yeah, I just repeated the exercise myself, and I discovered that noise needs to be eliminated unless you have a small file that can be displayed in full at 100%. Excessive noise adds a lot of dark values that disappear when downsampled. The noise influences the "original" histogram, but not the two "screen" histograms because they are already downsampled, killing the noise.   One way to get around this is to downsample the original RGB file before screenshotting the histogram, so that it fits the screen at 100%. That gets rid of the noise, the same way as for the other two image screenshots. In other words, this levels out the playing field.   Here's what I got (see the file names):   As you can see, Photoshop is pretty dead accurate. Lightroom (displaying the raw file) is ever so slightly off in the far darkest values, but there's no way I'm able to see that difference using Eizo coloredge monitors. For all practical purposes, these are identical.   Note that this measures the accuracy of the GPU/color management and your monitor profile combined. I don't know of any way to separate these two components. So if you don't get a match, rerun your monitor profiling first. ... View more

First open the file from Lightroom into Photoshop, in Adobe RGB. This is your original RGB file. The assumption here is that the raw file is correctly processed and encoded into Adobe RGB (there has never been any reason to doubt that).   The histogram for this Adobe RGB file is the reference. Make a screenshot of that histogram and keep it.   Next, take two screenshots of the image itself, one from Lightroom Develop and the other from Photoshop. If the monitor profile is already embedded here, you don't do anything, that's fine (on Windows a screenshot is untagged and you need to assign the profile).   Open both image screenshots in Photoshop, with the monitor profile embedded. Convert both from the monitor profile to Adobe RGB. So now you have two Adobe RGB files that started out as screenshots. The interesting part here is the histogram, so again screenshot those and keep them.   What you have now is three histograms. Since they now all refer to the same color space, Adobe RGB, they are directly comparable and if the images they come from are identical, the histograms will also be identical.   Here's the background for the procedure: The numbers sent to screen are no longer in the original color space, they have already been converted into monitor color space. So that's the correct profile here. However, numbers are color space specific, so to be able to compare these, they need to all be brought into the same color space.   EDIT addition: there is one factor that can introduce small differences, and that is noise. If the on-screen image is zoomed out/scaled down, different screen resampling algorithms can produce slightly different results. For this reason, either use a low-ISO image with very little noise (Denoise is an option here) - or use an image that is small enough to fit on screen at 100%. This isn't the reason for what you're seeing, but just to remove complicating factors from the equation.     ... View more

One other useful piece of information I found was from user rvdknl in the Apple forums. He says in the post "Lifted and desatured blacks in Photoshop" that switching from Adobe ACE to Apple CMM in PS's colour settings virtually fixes the issue. By @Jamie Farquharson   Yes, that has also been reported here. For some it corrects it completely, for others some of the way. Of course, both color management engines should produce the correct result. This isn't open to interpretation.   Figuring out which version you can trust should at least give you some firm ground. ... View more

This is an issue that has been reported from several Mac users lately. The symptom seems to be the same: excessive black clipping in Lightroom compared to Photoshop.   I would start by determining which of these two is the correct representation. That's pretty easy to determine. Take screenshots of both, assign your monitor profile, and convert back to Adobe RGB. All the 3 histograms - original Adobe RGB file and the two screenshots - should now be a perfect match. If they're not, the odd one out doesn't display the file correctly.   So far, all the signs point to a bug in MacOS - specifically, the GPU driver component in MacOS. It could be an Adobe bug, but if so, it's specific to the Mac Photoshop version. This has never been reported from Windows, and cannot be reproduced by Windows users who have tried (including myself).   And if, as you say, disabling the GPU clears it, that's further confirmation.       ... View more

Please post the full Help > System Info from Photoshop.   EDIT sorry, I see you already did. To be clear - did you try to completely disable the integrated Intel UHD 770? Conflicting dual GPUs is a known potential problem in laptops (depending on the laptop manufacturer's configuration).   ... View more

This is not normal, and there's no reason to accept it. You shouldn't need to relaunch Photoshop. It should not use more memory than you allocate in Preferences, plus scratch disk.   All the signs I've seen so far, reading the threads about it and trying to replicate (which I can't!) - points to the system pagefile. That's where this builds up, and what claims all this memory is the GPU. Of course, Photoshop <> GPU is a very tightly interwoven interaction, so a problem in one can be hard to separate from a problem in the other.   But again, clearing prefs has fixed it for many users. Others report that a new version didn't have the problem - which amounts to the same thing: fresh prefs.     ... View more

A few users have had this problem, and most of them have come back reporting that a full and complete reset of preferences has fixed it.   A full reset means moving the whole settings folder out of your user account, allowing PS to build new fresh settings. This returns Photoshop to clean, out-of-the-box factory state. Remember to save out actions, brushes etc.   The thing about preferences is that it contains a lot more than your own user settings - it's the complete application configuration, including lots of hidden and interdependent parameters. Preferences are rewritten on every exit, making it prone to corruption in irregular shutdowns. ... View more

OK, then it's a different issue. Yours is, as you say, clearly GPU-related.   https://helpx.adobe.com/photoshop/kb/troubleshoot-gpu-graphics-card.html  ... View more

Stephen is correct.   Photoshop isn't doing anything - but web browsers and consumer-oriented image viewers scale up when they detect a high resolution screen. Photoshop obviously can't do that.   This is the industry-standard workaround to ensure that the same material can be used regardless of the screen technology the user happens to have.   If not for this, we'd need two separate internets.   Set Photoshop to View > 200%. ... View more