Adobe Flash Player Stadnalone Projector acting wonky  

Yes, I know adobe said they'd drop flash last year but didn't/did(?), so I download the standalone flash player projector from this link, made the .swf files I got downloaded associated with the standalone player (mainly nsfw, some sfw, all im saying on that front), and when I double click and open the swf file, all I get is a white screen, and clicking on the file menu, I see in its pathline its running it as

Code:

C:\Users\NameHere\Desktop\EscapeRoomCustom.swf -relaunched

Now if I drag the swf file onto the standalone projector, it runs just fine, but I don't know why its doing this in windows 10 and compatibility mode doesnt work, it still adds on that -relaunched command line to it while running via double-clicking the swf file

Running windows 10 pro (64-bit) build number 18363.628, all updates applied (except the realtek audio update that kept installing itself, got tricky getting rid of it for good)

ill try that; its just weird tho; I tried it on my father's computer and it isnt giving me the -relaunched tag, although I did it by dragging the swf file onto it and didnt associate it with the swf file directly; worse case scenario the same thing happens on his computer and perhaps it isnt just me

- - - Updated - - -

No dice, deleted the "%1" tag from the command value first, and the projector returned only the -relaunched tag instead, so I deleted the registry value folder for the projector instead and restarted windows explorer via the task manager, re-associated the swf files with the projector, and once again got the -relaunched tag

I got no idea what's going on with this, but frankly, its dumb

BrokenDaily said:

deleted the "%1" tag from the command value first, and the projector returned only the -relaunched tag instead

Yeah, that was dumb on my part, as I now see other exe's in the Registry for associated commands, use this "%1" as the standard way to pass the filename to be executed.

You could try copying the 'flashplayer_32_sa.exe' to a different location and renaming it to something different. I recommend a copy, and not a just rename of the original because I seem to remember Windows sometimes will pass along the 'open with...' permissions of a renamed *.exe. I could be wrong there, but I tend to get superstitious with this stuff in Windows.

Then do another "Right Click > Open with... > More apps > Look for another app on this PC" to assoicate the open to this new copy instead and see what happens

I've been using the Projector for a while and have yet to see this '-relaunched' issue, but with dumb stuff like this you just never know when it might happen to you next, so keep me posted if you do find the underlining cause.

WAIT, figured it out; last time, I had to reinstall my amd drivers due to it missing a dll file or something, and to make sure, I copied that restored dll file to the folder I keep my programs in (the non-installable ones), it was an OpenCL.dll file, and for whatever reason, I think that dll file interfered with the flash player by adding that -relaunched command line argument. Well I archived that file into a .7z format, deleted said dll file, tried again, and its fixed now, can play .swf files again

didnt know that could interfere with the standalone flash player projector

- - - Updated - - -

and for the record, I wasn't calling your solution dumb Farvatten, I was calling this so-called un-needed command line addition to running swf files dumb (-relaunched), so im sorry if you took offense to it

Good find! Weird a *.dll in the same folder could do that, something to add to the list of things to consider in the future.

Thanks for posting the solution!

Actually I hadn't taken offense to your use of the expression 'dumb', I understood you were calling the '-relaunched' situation dumb, I just found the word convenient to use on myself after I realized my mistaken analysis of that "%1" command line option.

And I appreciate you taking the time to make this reassurance. ;o)

a last minute addon to this thread; while the problem with the standalone flash player seems to have been solved, when I tried doing this via the firefox browser (it has the latest firefox flash plugin installed btw), I still get the white screen problem

overall, it doesn't matter with me using .swf files with the firefox browser, so long as the standalone flash player projector works, i'll stay to using it until it has problems again

BrokenDaily said:

...when I tried doing this via the firefox browser, I still get the white screen problem

If your talking about opening a local *.sfw file in Firefox, I think that's normal. One of the reasons I went to the Projector for local files, is Firefox stopped supporting that a while ago. Here's what I get when I drag a *.swf into a browser window.