Cannot launch DSX after v3.1 Beta 1.43 update

[quasi trout]

Can you get me also the logs for the main app?

send me latest file from this folder

[blissful ivy]

@lean scroll

[lean scroll]

Reinstalled the beta once again (since i rolled back to non beta version) and after launching theres no logs in that folder after launching

[quasi trout]

you might have a hard crash issue

meaning some files messed up between switching

i would ty deleting the Main_v3_Beta folder fully, verify integrity files through steam, then relaunch DSX.

You could backup DSX_Savefile tho

[lean scroll]

okay ill try that

[lean scroll]

Still not launching, or getting any logs in the Main_v3_Beta folder, only getting logs updated for Launcher logs

[quasi trout]

and you're running the beta?

[lean scroll]

yes

[quasi trout]

need you to open Event Viewer and get me the application logs related to DSX that are errors

[blissful ivy]

You'll probably find errors related to dotnet runtime @lean scroll paste them as Screenshots with the message visible

If you know what to look for you can also paste the message content here directly

[quasi trout]

as example

[lean scroll]

okay ill try

no error like that

[blissful ivy]

Clear it, launch dsx, refresh events

[lean scroll]

cleared, relaunched, waited and refreshed but still nothing

[quasi trout]

very strange

[lean scroll]

rebooted pc, tried everything again , still no logs

nothing related to dsx i think

[quasi trout]

so the logs folder doesn't get created at all?

[lean scroll]

yes

only launcher logs get updated

[quasi trout]

that's like the first thing the app does when it runs, meaning something else is wrong

do you possibily have Anti-virus running that could be in play?

check to see if something complains about DSX

[blissful ivy]

Open Task Scheduler and share what you see, especially if there's a DSX Something entry

[quasi trout]

He won’t see anything there

According to this, task is made successfully, runs, and then deletes

Unless it never executes but deletes

[blissful ivy]

Maybe it is lying

[quasi trout]

But it says DSX_Launcher_Task completed execution

[lean scroll]

i only have windows security, no other antivirus and i tried putting dsx as an exclusion or turning off real time protection

[blissful ivy]

See my question above

[lean scroll]

nothing dsx related

[blissful ivy]

An Enigma for sure

Say, what happens if you were to manually run the DSX executable in the main beta dir?

Anything at all?

[lean scroll]

i got it running somehow

turned off run program as administrator in Main_v3_beta folder

and that got it running ig?

one in the main folder still on tho

but that worked ig

[blissful ivy]

Well run as Admin was terrible to begin with, how did that setting make it there

It doesn't come delivered and installed like that so you did that at some point in the past

[lean scroll]

i think i did it back when touchpad to mouse wasnt working when i used it in some games which made it work, i guess so yeah that was some time ago

[blissful ivy]

Good it's solved

[lean scroll]

anyways thank you for your time

[edgy sable]

i have the same problem Cryo did and i tried every he did and still doesn't work for

and never had it set to run as an admin

[celest grail]

it was the only way to use keyboard mapping on dualsense edge at 1.41/1.42

now this feature is completely broken

[blissful ivy]

Stop running your games as Admin then

Also once we switch to true KBM emulation, that nonsense will be a thing of the past entirely

[celest grail]

it not happen anytime soon (hours, days etc.)
and it work before, 2 updates broke it in different ways

[blissful ivy]

Explain your case, it's not supposed to be run as Admin. Ever.

Maybe we figure it out together

[celest grail]

it was all explained here https://discord.com/channels/836790685784211486/1333890923192385606

[blissful ivy]

Gotcha

[quasi trout]

i was gonna ask about the admin pop in the vid, but didn’t think much of it.

It makes sense actually and it doesn’t make sense

If you want DSX to stay admin, you’d need to convert the launcher to also be admin I think.

Then again, this isn’t at all needed when we get true KB/M emulation (hurry tf up ~nef~) ahem

[blissful ivy]

It's on the pile with everything else that can't be rushed by wishful thinking

[quasi trout]

Also @celest grail it’s not in my hand. Nothing regarding the input system, action system was touched with this update, I’ve said your solution, and it’s KB/M emulation coming soon

[blissful ivy]

Try it with the launcher also set as admin, other than that I do not see any other quick fix in sight

[celest grail]

wdym
which exe?

[blissful ivy]

The one in the root app directory

[celest grail]

same
it won't start

[blissful ivy]

Well, was afraid so

[quasi trout]

I’ll try to debug this soon

Task scheduler is the one failing

Even tho task is made and executed, something else is wrong

I’m thinking that there’s some admin thing to enable

Idk will see

[blissful ivy]

It's not surprising at all, task Scheduler can't magically launch an Admin process from a task that has been created as regular user, that's what the Run with highest privilege option is for. In theory if you set that with a launcher also running as Admin, it should work

You'd need to be very careful not mixing any of that up and track if the launcher was run as Admin, and if so, create the task with higher privileges as well

[quasi trout]

Easier to just have kb/m lol

[blissful ivy]

Probably

[quasi trout]

in case you guys were curious, task scheduler fails

[blissful ivy]

Yeah that confirms what I said earlier

You can not create a task as a regular user and then that task would try to trigger an executable explicitly marked to be run as admin

That would be the easiest privilege escalation vulnerability ever otherwise

Because Task Scheduler can not display the UAC prompt to the user either

[quasi trout]

other methods fail as well because DSX is admin which sounds normal

[blissful ivy]

WDYM other methods?

[quasi trout]

Using WMI (ManagementClass) fails as well

[blissful ivy]

Yes, ofc.

[quasi trout]

Method #4 does work tho, which is a simple process.start()

[blissful ivy]

Yeah because that happens in the user context

[quasi trout]

but launcher crashed because of another reason so just discovered that

[blissful ivy]

Task Scheduler and WMI do not

[blissful ivy]

Suggestion:

• Make launcher check itself if it was run as admin
• Check if the main executable is flagged as run as admin too
• If so, adjust task creation by setting run with highest privileges
• Now the entire thing should work again

That info can be found by querying the registry, some ChatSkibidi to the rescue:

using System;
using Microsoft.Win32;

class Program
{
    static void Main()
    {
        string exePath = @"C:\Path\To\YourApp.exe";
        bool isRunAsAdmin = CheckRunAsAdminFlag(exePath);
        Console.WriteLine($"Is '{exePath}' flagged to run as admin? {isRunAsAdmin}");
    }

    static bool CheckRunAsAdminFlag(string exePath)
    {
        return CheckRegistryForRunAsAdmin(Registry.CurrentUser, exePath) ||
               CheckRegistryForRunAsAdmin(Registry.LocalMachine, exePath);
    }

    static bool CheckRegistryForRunAsAdmin(RegistryKey baseKey, string exePath)
    {
        const string subKeyPath = @"Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers";
        using (var key = baseKey.OpenSubKey(subKeyPath))
        {
            if (key != null)
            {
                object value = key.GetValue(exePath);
                if (value != null && value.ToString().Contains("RUNASADMIN"))
                {
                    return true;
                }
            }
        }
        return false;
    }
}

Similar the self-check:

using System;
using System.Security.Principal;

class Program
{
    static void Main()
    {
        if (IsRunningAsAdmin())
        {
            Console.WriteLine("The process is running as an administrator.");
        }
        else
        {
            Console.WriteLine("The process is NOT running as an administrator.");
        }
    }

    static bool IsRunningAsAdmin()
    {
        using (WindowsIdentity identity = WindowsIdentity.GetCurrent())
        {
            WindowsPrincipal principal = new WindowsPrincipal(identity);
            return principal.IsInRole(WindowsBuiltInRole.Administrator);
        }
    }
}

[quasi trout]

okay will try the above, if launcher is admin, will give task admin level so that it can launch DSX properly

[quasi trout]

okay i have improved it

[edgy sable]

it still won't boot for me

[blissful ivy]

Well, have you followed the thread and checked you are not marking the executables as Run as Admin?

[edgy sable]

yes

i never had it set to run as an admin and i completely uninstalled with revounistaller and it still won't boot

[blissful ivy]

You revounistaller did what?

Please explain

[edgy sable]

it removes all files related to the program including reg changes

[blissful ivy]

What exactly did you use that thing with (I doubt it did anything anyway)?

DSX doesn't use the registry and every Steam app is a portable app, there is nothing any of those weird 3rd party tools could do "better"

Have you seen anything in event viewer, application logs?

[edgy sable]

no

[blissful ivy]

Don't let me pull everything out of your nose, it is exhausting. What exactly are you doing and what is happening, describe or make a video even

Are you on the Beta or regular channel?

[edgy sable]

yes

give me a minute

it did show something in event viewer this time but i'm not show if it's related

https://streamable.com/beed31

[blissful ivy]

Are logs produced?

[edgy sable]

yes

[blissful ivy]

Then share the most recent one here pls

That is not what I meant, in the app directory there are logs subfolders with text files in them, share those, not whatever that blob was

[edgy sable]

then no nothing like that was produced

[blissful ivy]

Bloody hell

U sure?

Did you look there?

[edgy sable]

is that it

[blissful ivy]

Is it from today?

Ah according to file name we should be good, lemme check it out

Aha!

2025-02-13 08:52:18 [ERR] Error in creating and running the scheduled task.
System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
   at Microsoft.Win32.TaskScheduler.V2Interop.ITaskFolder.DeleteTask(String Name, Int32 flags)
   at Microsoft.Win32.TaskScheduler.TaskFolder.DeleteTask(String name, Boolean exceptionOnNotExists)
   at DSXLauncher.MainWindow.<LaunchingDSX>d__17.MoveNext()

@edgy sable fire up Task Scheduler

[edgy sable]

now what

[blissful ivy]

Find anything DSX in the name in the list, share screenshot

[blissful ivy]

Let me finish typing

[blissful ivy]

[edgy sable]

ok

[blissful ivy]

What is that

Just paste a PNG into discord, mate

ShareX, Greenshot, SnippingTool, .... all those can do that in 2 seconds

[edgy sable]

ok

[blissful ivy]

First entry, DSX_.... right click delete or remove or however it is called

Then retry runing DSX

[edgy sable]

okay it worked

[blissful ivy]

[blissful ivy]

@quasi trout another case to take care of: if a task already exists and has previously been created with elevated privileges, the launcher now can no longer overwrite it, so if you get that exception, tell the user how to fix with a dialog instead of silent fail

[blissful ivy]

NVM I fixed it in dev

[quasi trout]

NOTHING WAS PUSHED TO STEAM

I haven’t yet updated the launcher to handle DSX as admin etc..

[blissful ivy]

Yeah it's OK, we fixed it "by hand"

[quasi trout]

Ah

Cool

[blissful ivy]

You are late, the house already burned down

[quasi trout]

Silent update was pushed to steam for v3.1 Beta for launcher issues

[grave dagger]

Hi, i have the 3.1 beta but can't find where to do the input text file for cyberpunk enhanced dualsense 5. It doesn''t work and I can only make it work with 2.5 version.

but with delay on the audio haptic, any fix for this?