Update to 25.2.0 The embedded ICC profile cannot be used because the ICC profile is invalid

@NB, colourmanagement No disagreement with you there, you're absolutely right - however, there are scenarios where this is the way to go, or doing a conversion would cause problems with third-party software. It's definitely not the way I prefer to work, and most of the time I don't - but it's absolutely important to be able to work with images in input color spaces.

@D Fosse whilst I agree that converting to a working colourspace within the capture SW can be very useful it's not for everyone. Some like to assess whether using, say, Adobe RGB will clip the data and choose a larger workingspace. Joseph Holmes has made a whole set of rather sophisticated working colour spaces which require an unconverted input file to assess which is needed.  

Say one was making a camera input profile, that would also require an unconverted file, as it may need a little spotting opening in Photoshop unconverted is vital. 

@courageous_youth15A7 You'll see above that I agree with you in the main, however, it should be noted that the experience of many dictates that colour and tonal correction of images whilst in a potentially non-linear input colourspace can give some rather unwanted and unpredicted results. Hence the "standard" workflow of only making colour and tonal corrections on images when in a working colour space.

I hope this helps
neil barstow, colourmanagement net - adobe forum volunteer - co-author: 'getting colour right'
google me "neil barstow colourmanagement" for lots of free articles on colour management

@davidtavcar @courageous_youth15A7 I've posted a bug report about the input profile issue, please contribute to that thread and let's get it noticed:

https://community.adobe.com/t5/photoshop-ecosystem-bugs/photoshop-cannot-use-input-icc-profiles-scanner-and-camera/idi-p/14293693

reinstalling PS v25.1 regains the ability to use Input profiles. 

I hope this helps
neil barstow, colourmanagement net - adobe forum volunteer - co-author: 'getting colour right'
google me "neil barstow colourmanagement" for lots of free articles on colour management
Help others by clicking "Correct Answer" if the question is answered.
Found the answer elsewhere? Share it here. "Upvote" is for useful posts.

No, you do not - and there are workflows or specialized work where one would like/needs to keep everything in camera input space - photographic reproduction, or keeping color space conversions to an absolute minimum for example. This isn't particularly exotic, you can find this in pretty much every textbook about color management.

Furthermore: this was supported without any problems by Photoshop until now. It's a crucial feature for a color managed application, not an optional one.

Why would you use a camera input profile from Capture One? No surprise that this is rejected in Photoshop.

You need to output to a standard color space - sRGB, Adobe RGB, ProPhoto, Image P3.

Same problem over here with files exported from Capture One Pro with the camera input profile embedded - same error. This is true for both Beta and non-beta Photoshop.