Not exactly “Editing” - but related.
Opening RAW images in MS Photos, they initially display as shot … then, after about a sec, they change to some automated “processed” version.
It’s a bloody middle of the night pic that I want to be dark - and Photos displays what IT thinks it should look like (which is terrible!).
Is there some way to prevent it displaying it’s take on how it should look?
Never noticed this before because I rarely use to look at more than very briefly.
Why noy change your default photoviewer to one of the plethora of free and open source viewers?
I currently use ImageGlass which happily opens most image formats.
Because Photos is a shit load quicker than ImageGlass, for one reason.
What I suspect is happening is that when it opens them it’s showing you the embedded preview - which is a JPG that reflects your shooting settings - as a holding image while it loads and renders the RAW data, then it’s switching to the actual RAW data, ‘as is’ which is flat because it doesn’t know how you want to process it.
I think the embedded thumbnail idea is correct.
But version it ends up with isn’t the flat RAW. It’s a lot closer to clicking Auto in PS/LR … and that processing is supported by the time it takes.
And, being a night shot with dark skies and a few lights on a tower, it ends up with none of the things that should be dark being anywhere dark.
If only there was an “As shot” setting.
Looks like there was, but isn’t any more…
Ah - bummer!
See - it’s never bothered me before, and that article is 18 months old.
Thanks for finding that, though. 
Is this of any help?
I’m on Win10 - and that’s to do with adjusting the computer screen brightness?
I’ll look at a little closer, though.
Nope - no change. 
Hmm,beats me why would MS do such a thing and make it permanent.
It does seem totally illogical.
Doing a system restore since all that mumbo jumbo can’t have been beneficial to my laptop.
Oops, sorry 
I had the choice not to dive off the cliff … at night … in the fog … without checking if the tide was actually in or not.
Aaaaand, we’re back …
