Windows 7 problem with 6.2.0.2.

partyvan

I am getting a kernel32.dll error after upgrading to 6.2.0.2. on windows 7. Streamfab would not load and I get an error pop up.
Please see attached image. Thanks.

Brozilla

i mean 32bit vs 64bit

partyvan

i mean 32bit vs 64bit
Brozilla

This is 64x version.

Brozilla

This is 64x version.
partyvan

then why win7

Germania

[quote]StreamFab 6.2.0.2 Changelog
New: Some improvements on the Built-in Browser Engine of StreamFab.[/quote]
6201 used CEF 102.0.10.0
6202 use CEF 128.4.8.0

So 6202 with Chrome Embedded Framework v128 not works for Win7

Chrome 109 is the last version to support Windows 7 - source

NewMelle

I initially got around the Win7 issues by installing VirtualBox and a Win11 virtual machine to run more recent apps (which is what I used to troubleshot and migrate my Win7 apps/audio plugins to 11). The only other option is to move to a more recent abomination of Windows. I've since updated my primary workstation to a stripped down de-stupified de-GamR-ed Win11 but can dual boot Win7 when needed.

I think it is time (now that the CEF is 128) StreamFab removes the claim of supporting Win7/8/8.1. Although most of us regulars are accustomed to the constant barrage of BS and false claims new customers are not as wary or seasoned.

then why win7
Brozilla

Not quite sure what this has to do with x64 vs x86. There again I'm not fluent in GamR.

Germania

.. Although most of us regulars are accustomed to the constant barrage of BS and false claims new customers are not as wary or seasoned.
NewMelle

yep

So I agree - but without information for those affected, that's not okay.

And the StreamUpdate should detect Win7 and block 6202 Upgrade.
Germania

NewMelle

Agreed 100%.

The first thing I do when installing a new version of SF is to cripple StreamUpdate.exe. I can't recall the last time the built in updater actually worked properly. Maybe in 2021 or 2022 but not for a LONG time.

AGuyWithAComputer

I
Not quite sure what this has to do with x64 vs x86. There again I'm not fluent in GamR.
NewMelle

x64 is 64BIT x86 is 32Bit. Not a gamer thing. But Windows 7 was typically a 32bit install. it was rare to find someone with the 64bit variant.

Brozilla

I
Not quite sure what this has to do with x64 vs x86. There again I'm not fluent in GamR.
NewMelle

x64 is 64BIT x86 is 32Bit. Not a gamer thing. But Windows 7 was typically a 32bit install. it was rare to find someone with the 64bit variant.
AGuyWithAComputer

what he says and:
because there are no more 32bit systems under win10/11
there is also absolutely no reason to stay on windows 7
no security updates (windows 10 also ends next year)
many programs will no longer run on windows7 etc

the pin on how to install and run streamfab on win7 is also unnecessary.

AGuyWithAComputer

what he says and:
because there are no more 32bit systems under win10/11
there is also absolutely no reason to stay on windows 7
no security updates (windows 10 also ends next year)
many programs will no longer run on windows7 etc

the pin on how to install and run streamfab on win7 is also unnecessary.
Brozilla

Isn't that pin Mel's how to install Windows 11 on a depreciated hypervisor on windows 7? but yeah, it could be removed. There are easier ways to get around the requirements of windows 11 and install right on the hardware.

Windows 10 does have a 32 Bit variant, but it is rare. Who has a system with less that 4GB or RAM now a day's anyway.

But you are correct Windows 10 22H2 is out of support by this time Next year. All preceding versions of Windows 10 are already out of support.

Germania

the pin on how to install and run streamfab on win7 is also unnecessary.
Brozilla

It was removed from Stickies:

Running StreamFab Inside Win7 Hosted VirtualBox

MidnightInAurora

Win 10 IoT Ent LTSC 2021 will have security updates until 2032. The ISO is avail on the archive and MAS is your friend.

Germania

and Win10 Home/Pro get 3 years (paid) ESU (Extended Security Updates)

Stan001

I think SF made yet another mistake supporting Win 7 this long.
The operating system is not supported by Microsoft, I barely remember since it's been so long php dropped support, py is going to, if not already, dropped support 99% of everybody has dropped support. There may be several ways to do Windows 11, and I understand NewMelle and why he keeps Win7, and he did at least go to the trouble to tell others with Win 7 and the same can be done for those who use Win 10 to go to Windows 11 and keep their current versions of Windows.
From what I recall, NewMelle finally went to dual booting Win7 and Win11. I still like VM's there is not much to making them and maintaining them and not having to even dual boot.
I used VM's for a long time, had even a Win XP VM as well as other OS including Ubuntu VM's.
I had to get a new computer, and it was not long after Win11 came out, I was not thrilled and YES Win11 has issues, but it will be the only OS Microsoft will keep supporting, with no charge, until they may change to Win 12, which Win 12 still seems like a pip dream.

So people have no choice in some way or another whether a new computer even refurbished one or using VM or maybe some other method they need to move to Win11 to use 99% of new software including later versions of SF and other programs similar.

Anyone wanting to upgrade any computer to Win11, google Rufus to make a USB boot setup that will install Win11 on non-compliant computers.

NewMelle

x64 is 64BIT x86 is 32Bit. Not a gamer thing. But Windows 7 was typically a 32bit install. it was rare to find someone with the 64bit variant.
AGuyWithAComputer

I understand x64 and x86. Maybe in your neck of the woods x86 Win7 was common. I personally have never done a 32 bit install of Win7 and I've done thousands of installs in Win7s lifetime. Entire networks migrating from XP and Win2000 (few businesses were stupid enough to adopt Visturd).

That pinned topic has thankfully been gone for a long time and I took that info down. Too many people got their panties in a bunch over it.

VirtualBox is not VmVomit. Last I checked VirtualBox is not deprecated and still in active development. I use it to this day.

Although I am now running Win11 I'm not going to become one of these narrow minded pompous holier-than-thous that shits on Win7 and scorns/chastises Win7 users.

I completely understand wanting to hang on to Win7. I lost approximately $1600 in paid DAW plugins as the Win10/11 versions are designed for morons and painfully laughable. I realize there are those who say there is no reason to stay on Win7 but I also attribute that to lack of experience or knowledge and take it with a grain of salt. Some older programs simply don't run properly on later versions of Windows.

By the same token I also completely understand SF moving away from supporting Windows7. It has gone the route of 98SE, XP and NT 40. My point there is at least be honest about it for future customers.

Come October next year I am going to take great pleasure watching Win12/Win-Umpteen users raking Win10 users over the coals for not "upgrading" to the latest and greatest debacle/trojan/malware/spyware from Redmond. I hope those assholes remember me then. ;)

My point there was the minute the OP indicated the install was X64 the Win10 poindexter came out gunning for Win7 instead of offering alternatives or solutions.

If a member wants to hang on to Win7 as long as possible I am more than happy to help them out any way I can. I will PM them and if interested restore the VBox solution pages so they can begin the process I had to go through to ultimately migrate to Win11.

Isn't that pin Mel's how to install Windows 11 on a depreciated hypervisor on windows 7? but yeah, it could be removed. There are easier ways to get around the requirements of windows 11 and install right on the hardware.
AGuyWithAComputer

If you're referring to the LabConfig registry entries I covered that. Rather than simply mentioning there is a way to get around the Win7 issues why not share some of that vast knowledge so others may benefit from it. I put a lot of time and effort into the VirtualBox solution and to date not received a dime for the work (nor asked for it). I did it for others in the same boat I was in.

If installing Win10/11 fresh the following site is your friend.

https://schneegans.de/windows/unattend-generator/

The VirtualBox solution allowed me to migrate one program/plugin at a time form Win7 to Win11. It granted me the reprieve necessary to get everything ready for Win11 before I committed to it.

If it's any consolation I have a Win7 Pro VM set up for those few programs that simply refuse to kiss Win11s ass. ;)

october262

I am getting a kernel32.dll error after upgrading to 6.2.0.2. on windows 7. Streamfab would not load and I get an error pop up.
Please see attached image. Thanks.

partyvan

try this -

Re-register kernel32.dll: Run the command regsvr32 kernel32.dll in the Command Prompt with administrator privileges to re-register the DLL file.

then try running streamfab and see if it'll run on windows 7

there is also a program that allows you to run newer apps on older operating system such as windows 7 & vista
called windows 7 extended kernel - https://www.sevenforums.com/drivers/429406-discard-virtual-memory-dynamic-link-library-kernel-32-dll.html
post #6

NewMelle

OK, that's a new one on me. THANKS! I still get messages from people running Win7 hitting version roadblocks. I'm curious if it will work with SF and it's embedded CEF.

Germania

I don't think the installation is the big problem - but Chrome 128 will probably still not work (without errors).
But it would be worth a try for those affected...

AGuyWithAComputer

That pinned topic has thankfully been gone for a long time and I took that info down. Too many people got their panties in a bunch over it.

VirtualBox is not VmVomit. Last I checked VirtualBox is not deprecated and still in active development. I use it to this day.
NewMelle

No it's Oracle vomit instead. You're better off with Hyper-V. As I recall the version you linked was depreciated since the latest won't run on 7.

My point there was the minute the OP indicated the install was X64 the Win10 poindexter came out gunning for Win7 instead of offering alternatives or solutions.

If a member wants to hang on to Win7 as long as possible I am more than happy to help them out any way I can. I will PM them and if interested restore the VBox solution pages so they can begin the process I had to go through to ultimately migrate to Win11.

NewMelle

SF updated the version of Chromium to one not supported by Win7. This program will no longer run on Win7 is the correct answer. Are their other ways around it? sure. Are they simple? not really.

If you're referring to the LabConfig registry entries I covered that. Rather than simply mentioning there is a way to get around the Win7 issues why not share some of that vast knowledge so others may benefit from it. I put a lot of time and effort into the VirtualBox solution and to date not received a dime for the work (nor asked for it). I did it for others in the same boat I was in.

If installing Win10/11 fresh the following site is your friend.

https://schneegans.de/windows/unattend-generator/

The VirtualBox solution allowed me to migrate one program/plugin at a time form Win7 to Win11. It granted me the reprieve necessary to get everything ready for Win11 before I committed to it.

If it's any consolation I have a Win7 Pro VM set up for those few programs that simply refuse to kiss Win11s ass. ;)
NewMelle

The way to get around the windows 7 problem is to get off windows 7. I know it's not what you want to hear, but the truth hurts. All of the effort you put in was to a problem you invented.