Vortex 1.6.1 Beta white screen flash + auto restart Vortex

[DarkDominion]

Good evening

Also posting this separately because it's a "new" issue for a newer version.

Vortex 1.6.1 Beta

Released on 7/7/2022
Electron 19.0.7

Node 16.14.2

Chrome 102.0.5005.134

 

Trying to install a new mod makes Vortex flash with a white screen and it restarts immediately.
Mod is still trying to install : " Installing Bretonnia - New Breton Presets (.esp)-70820-1-0-1657051954 - Preparing.... " (or any other mod)

A warning then says : " Vortex restarted after a crash, sorry about that. "

Also this :
" The last session of Vortex logged an exception.

Please visit this thread for typical reasons causing this.
Please report this issue only if you're sure none of those reasons apply to you! "

 

From the Vortex.log :

Thu, 07 Jul 2022 16:26:08 GMT - debug: extraction completed

Thu, 07 Jul 2022 16:26:08 GMT - info: listen pipePath=\\?\pipe\H1xKXFF4s9
Thu, 07 Jul 2022 16:26:08 GMT - info: listen pipePath=\\?\pipe\H1xKXFF4s9_reply
Thu, 07 Jul 2022 16:26:08 GMT - debug: [installer] waiting for peer process to connect pipe=true, ipcId=H1xKXFF4s9
Thu, 07 Jul 2022 16:26:08 GMT - info: failed to grant access WinApiException: Unknown error
Thu, 07 Jul 2022 16:26:09 GMT - debug: [installer] peer connected there
Thu, 07 Jul 2022 16:26:09 GMT - info: there channel connected
Thu, 07 Jul 2022 16:26:09 GMT - debug: [installer] peer connected reply
Thu, 07 Jul 2022 16:26:09 GMT - debug: [installer] peer connected there
Thu, 07 Jul 2022 16:26:09 GMT - info: there channel connected
Thu, 07 Jul 2022 16:26:09 GMT - debug: [installer] peer connected reply
Thu, 07 Jul 2022 16:26:09 GMT - info: from installer: Unhandled exception.
Thu, 07 Jul 2022 16:26:09 GMT - error: render process gone exitCode=-1073741819, reason=crashed

Actions taken :

I've run the .NET Framework Repair Tool.

After that I reinstalled .NET Framework 4.8 which was inconclusive because the Repair Tool already fixed that.
Also repaired .NET 6.0 just to make sure

 

Prior to this all Vortex was working well even after the latest Windows Update.
So it must be something in the 1.6.1 Beta that's not working well ?

 

Hope this can be fixed.
Cheers
-=DD=-

[DarkDominion]

Install exactly this file :
.NET 6.0.7 [ EDIT : 6.0.7 is now the newest version ]

[Pickysaurus]

I've had a similar problem on my home PC, so will try and replicate it. Have you also submitted this via the in-app feedback system?

[DarkDominion]

I've had a similar problem on my home PC, so will try and replicate it. Have you also submitted this via the in-app feedback system?

Hey Picky, sorry for the late reply :smile:

 

I did not get a warning that my .NET 6.0.0 version was outdated too old for this new Vortex release ( not sure if it's only the Beta btw ).

But it's fixed with installing .NET 6.0.6

And yes, I did submit a ticket to support for this issue, with the exact text as in my OP.

I did not submit a ticket for the skse_64 2.1.5. version warning but I saw you already posted the issue on GitHub, thanks :wink:

 

There was an update which fixed the "no message on .NET installation" issue and the "skse_64 2.1.5." issue :

 

Changelog for 1.6.2 (12 July 2022)

Bugfixes:

• crash installing mods for some users
• exception attempting to determine game version if game not (no longer) discovered
• exception installing mod if game version can't be parsed
• exception if user cancels required .NET 6 download
• (very rare) exception upon reinstalling mods
• OBSE/NVSE got downloaded even when the notification was dismissed
• mods could show as "unsolved dependencies" if their rules included a conflict with the mod itself
• mod rules targeting version ranges could be detected as matching when they shouldn't
• startup check for .NET 6 didn't trigger if non-desktop variant of .NET already installed
• no reportable notification when Vortex recovered after a crash
• ea/origin game store didn't support certain game manifests ( those not encoded with utf-8 )

Improvements:

• dropped the startup message (on first start) about collections being introduced in 1.5
• (Dragons Dogma) will now merge mods modifying title.arc

API:

• no longer emitting mod-enabled/mod-disabled events for uninstalled mods

Cheers

-=DD=-

[Pickysaurus]

Glad to hear it. I'm still having this issue on my home PC and Tannin is helping me with it, but it's slow going as he gives me something to try during the work day, then I try it at home later and give him the results the next day. I believe we've stopped the "white flash" and reboot, but we're still trying some things.

[rmm200]

Wack-a-mole. Glad you guys are having good luck nailing the critters.

I think I will stay off Beta for a bit...

[DarkDominion]

Glad to hear it. I'm still having this issue on my home PC and Tannin is helping me with it, but it's slow going as he gives me something to try during the work day, then I try it at home later and give him the results the next day. I believe we've stopped the "white flash" and reboot, but we're still trying some things.

 

What I did :

Download Microsoft .NET Framework Repair Tool and run it.

Download .NET Framework 4.8 Runtime and install it if necessary.

Download .NET 6.0.7 (latest version)

 

If I understand correctly : you need .NET 6.x.x runtime

Hope this helps ?

 

Cheers

Edited July 14, 2022 by DarkDominion

[Pickysaurus]

Thanks DD, but I am pretty sure I know how to fix it myself, I've just left my PC is broken state to play the role of a user who wouldn't know how.

 

As long as you have a full install of .NET 6 the beta works fine.

[Tannin42]

.NET Framework 4.8 isn't a requirement for Vortex anymore but for the time being, Windows usually ships with some version of .NET Framework 4 anyway so it doesn't hurt to have the latest version on your system.

[DarkDominion]

 

Thanks DD, but I am pretty sure I know how to fix it myself, I've just left my PC is broken state to play the role of a user who wouldn't know how.

Ah, that I did not know

Sorry @Picky

 

 

.NET Framework 4.8 isn't a requirement for Vortex anymore but for the time being, Windows usually ships with some version of .NET Framework 4 anyway so it doesn't hurt to have the latest version on your system.

Thanks for the elaboration @Tannin

I'll correct my posts

 

Cheers all, and thanks for the efforts and fixes !