StreamFab for Windows StreamFab 6.2.4.7 Continually Crashes

[littlebluealien]

Guys, I need your help.

I installed the latest version 6.2.4.8 and have found it so buggy that I decided to do a clean uninstall and reinstalled 6.2.4.7. But ever since I've reinstalled 6.2.4.7, every time I try to open the Amazon Prime module, it crashes 6.2.4.7 completely.

What's going on?

H E L P!!

StreamFab.zip

[Germania]

But ever since I've reinstalled 6.2.4.7, every time I try to open the Amazon Prime module, it crashes 6.2.4.7 completely.

The same thing happened to me with 6247 after I used 6248 for HBO Max ..
.. I copied all the 6247 files from my backup, but nothing changed.

A new temp folder (autocreated by SF after rename the old) worked for me - see also here

[littlebluealien]

The same thing happened to me with 6247 after I used 6248 for HBO Max ..
.. I copied all the 6247 files from my backup, but nothing changed.

A new temp folder (autocreated by SF after rename the old) worked for me - see also here

Germania, quick question .. Do you wear a cape? Coz you certainly swoop in to the rescue like Superman lol. That [was] a compliment.

Well misery loves company, so I was actually mighty relieved to read that you experienced the exact same issue after uninstalling the dreadful 6.2.4.8! Made me realise the issue [was] the new update and nothing I was doing .. ANYWAY, the reason for this is to say I've fixed it! I might not be as tech savy as most on this forum, but I will certainly not let something like this beat me without giving it a good go at resolving it.

I used (as normal) Revo Uninstaller to remove 6.2.4.7 and then followed the removal with a Forced uninstall (again through Revo), making sure anything StreamFab was completely gone from my pc. Restarted the pc and did a fresh install of 6.2.4.7 after redownloading it from my DVDFab extended download service. All personal settings were gone. I had to reauthorize the new installation. This resolved the issue, so Wilson.Wang, there is a serious problem with the latest update 6.2.4.8. It's bugged out and this needs serious attention as it's affecting installs of previous versions from working.

But again, as previously said, THANK YOU Germania. You. Are. Greatly. Appreciated!

By so many of us.

[simchris]

Anecdotally, on Windows, I find *installing* the app (with offline installer) as admin works better than trying to run as admin after the fact, when there are oddball write permission issues. In my case I also create my own temp/cache directory which I then point SF at, so it can create dependencies but not the root folder for this stuff. Probably nothing to do with your troubles, but this works for me.

[jpp72]

Anecdotally, on Windows, I find *installing* the app (with offline installer) as admin works better than trying to run as admin after the fact, when there are oddball write permission issues. In my case I also create my own temp/cache directory which I then point SF at, so it can create dependencies but not the root folder for this stuff. Probably nothing to do with your troubles, but this works for me.

Another thing that breaks when running as an administrator is that you cannot use SMB shares that have been mapped as a network drive. SF simply doesn't see them.

[littlebluealien]

Another thing that breaks when running as an administrator is that you cannot use SMB shares that have been mapped as a network drive. SF simply doesn't see them.

jpp72 simchris Firstly thank you guys for your support and input -seriously appreciated and gratefully received. Just to clear up the Admin thing -the ONLY REASON I got into the habit of 'running as Admin' was due to "tech support" responses to tickets I've raised with them on occasion and their insistence that I run StreamFab as Admin to resolve issues being experienced. But as another post of mine pointed out, it soon became apparent that their insistence to "run as Admin" seemed to be the 'fix' for [all] issues being experienced rather than them doing proper support and feedback to the Dev. I'm now NOT running as Admin. 6.2.4.7 is working fine again since the reinstall, but 6.2.4.8 just will not allow me to use the Amazon module -it just will not load and open correctly. I'm sticking with 4.7 and waiting on the next update.

[Sebastian001]

Maybe it makes a difference whether you're using Windows 10 or 11. I'm using Windows 11 26100.4770, and the Amazon module works for me. However, I have to close and reopen Streamfab for each module, otherwise the browser won't load the pages.

[littlebluealien]

Maybe it makes a difference whether you're using Windows 10 or 11. I'm using Windows 11 26100.4770, and the Amazon module works for me. However, I have to close and reopen Streamfab for each module, otherwise the browser won't load the pages.

Windows 10 Home. The fact that you have to continually close and reopen StreamFab just so each module's browser loads properly sounds like 6.2.4.8 is broken to me! However, 6.2.4.7 works perfectly without the need to close and reopen [anything]. I'll stay with what works like I said, until the next update -hopefully without the need to mess about just to get something to work as it should.

But, again, I do take some comfort from the fact that other more notable users than I, yourself and Germania for instance, are also experiencing issues with the new update that aren't prevalent in 4.7. So it's 4.8 that's buggy. And again, thanks for your invaluable input my friend. Appreciated. Genuinely.

[Sebastian001]

Windows 10 Home. The fact that you have to continually close and reopen StreamFab just so each module's browser loads properly sounds like 6.2.4.8 is broken to me! However, 6.2.4.7 works perfectly without the need to close and reopen [anything]. I'll stay with what works like I said, until the next update -hopefully without the need to mess about just to get something to work as it should.

But, again, I do take some comfort from the fact that other more notable users than I, yourself and Germania for instance, are also experiencing issues with the new update that aren't prevalent in 4.7. So it's 4.8 that's buggy. And again, thanks for your invaluable input my friend. Appreciated. Genuinely.

Yes, but my problem has been with me for several versions now, and it has nothing to do with 6248. Well, it's not really a problem, since I know how to deal with it...

[littlebluealien]

Yes, but my problem has been with me for several versions now, and it has nothing to do with 6248. Well, it's not really a problem, since I know how to deal with it...

My friend, THANK YOU. As strange as this is gonna sound, what you wrote in your response kicked me up the ass and motivated me to again try and resolve the issue I had been experiencing with the latest update. Thorough clean uninstall, which I always do, especially after the great advice from many users on here about the importance of removing EVERYTHING related to the version being replaced. Seems I hadn't been as thorough as I had initially thought, despite [always] using Revo and CCleaner Pro in the process. 6.2.4.8 reinstalled [offline -as always], but this time no issues, especially with the Amazon module. Oh and big difference this time was I never installed as Admin (screw tech support) and now open as norm, no Admin. And it works like a dream. So again, thanks for your words. I know it wasn't probably your intention to kick me up the ass, but your boot did the trick either way!! One more aspect of the great support on the forum vs. tech support tickets -they don't offer their boot up the behind as a motivator!!

[AGuyWithAComputer]

Another thing that breaks when running as an administrator is that you cannot use SMB shares that have been mapped as a network drive. SF simply doesn't see them.

It's not just a SF thing; I've run into this issue multiple times with other software where I have manually mapped a share to a drive letter in user mode. It'll crop up when you use a different user to authenticate to the share or the same user with different password. I work around it by using "net use x: \\share\path" in an elevated command prompt adding user creds and persistence flags as needed.

[jpp72]

It's not just a SF thing; I've run into this issue multiple times with other software where I have manually mapped a share to a drive letter in user mode. It'll crop up when you use a different user to authenticate to the share or the same user with different password. I work around it by using "net use x: \\share\path" in an elevated command prompt adding user creds and persistence flags as needed.

I know that. I just pointed out that SF is not different in that regard. My downloads, pictures, documents and videos folders are on a shared mapped drive access by all my computers (5 servers and 9 workstations/laptops) and let's say i want to run my Easy MOD from there, i gotta do like you said with net use.

Although there are some very technically strong people here, most are not... At least that's my impression from some of the questions and speculations posted lol

[AGuyWithAComputer]

Although there are some very technically strong people here, most are not... At least that's my impression from some of the questions and speculations posted lol

This is true.

[MrGrackle]

A new temp folder (autocreated by SF after rename the old) worked for me - see also here

This is a royal pain in the ass for some though because of the great difficulties of getting NF to log back in again. Grrrrrrrrr.