Shellexecute stopped working "properly" for me

[Champak]

I have this simple line to launch a jpg using windows Photos, ShellExecute($DisplayPhoto1[0]) (The variable is a path to a jpg). Windows did that stupid update a couple nights ago and ever since then every time this executes the window pops up asking what app I want to use to open the file. I select the Photos app and check the always use this app, but even though I check the always use this app, this window keeps coming up. Now if I go and click a jpg file directly, the image opens up in Photos without any issue. What has happened? What can I do to fix or work around this? And no, I can't do a windows roll back because for some reason all of my windows recovery points were wiped out even though I have over 200G of free space smh.

I also tried: Run(@ComSpec & " /c rundll32.exe C:\Windows\System32\shimgvw.dll,ImageView_Fullscreen " & $DisplayPhoto1[0]) but that doesn't work for me because it actually opens a different app and command prompt.

EDIT: I also checked the default app settings and it shows that Photos is set as the default for jpg files, but this popup window keeps coming up asking me which program I want to use.

Edited November 25, 2023 by Champak

[CYCho]

Did you check the default app to open jpg file in the Windows Settings?
https://www.howtogeek.com/746203/how-to-set-your-default-apps-on-windows-11/

[Champak]

yes...and I'm using Win10

Edited November 25, 2023 by Champak

[argumentum]

Just tested both:
start "this.jpg" opens my default handler.
rundll32.exe C:\Windows\System32\shimgvw.dll,ImageView_Fullscreen "this.jpg" opens Windows Photo Viewer.

What you claim should be impossible, since you're calling shimgvw.dll. No clue of what's going on. Using Win 10 (2004) here. What version are you using ?.

[Champak]

I'm looking in the windows specifications in the settings about area and it doesn't say the year but it is Win 10 Pro version 22H2 build 19045.2965

[Resiak1811]

try :

$command = @SystemDir & "\Rundll32.exe Url,FileProtocolHandler " & $DisplayPhoto1[0]
Run($command)

 

[Champak]

same thing

[Resiak1811]

do a :

ClipPut($DisplayPhoto1[0])

and paste your result .. want to see the path please

[Champak]

It's just a basic path...I did your suggestion in a file by itself.

$command = @SystemDir & "\Rundll32.exe Url,FileProtocolHandler " & "C:\Users\User\Desktop\Newfolder2\IMG_5301.jpg"
Run($command)

Anyway, I went into Recovery and did an advanced startup and uninstalled the update from there...I forgot about this area. That fixed the problem (uninstalling them from control panel wasn't working). What I don't understand is why these damn updates are always sneaking onto my system. Every time I think I defeated one of these auto updates and update proofed my computer, BAM I get another one. Why can't microsoft leave me alone!?!

[Resiak1811]

hehe Dear Microsoft!

 

Leave your post open so maybe another user will have a better idea..