Skip to content
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Donate
Collapse

Plutonium

  1. Home
  2. Launcher Support
  3. Plutonium.exe does not run. First time setting up.

Plutonium.exe does not run. First time setting up.

Scheduled Pinned Locked Moved Launcher Support
13 Posts 3 Posters 393 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • no romeundefined Offline
    no romeundefined Offline
    no rome Contributor
    wrote on last edited by no rome
    #3

    Dss0

    where is the launcher stored?
    d1fb4ec2-635d-4959-b54e-45688c9d704a-image.png
    On my desktop, as suggested by the website.

    Does the filepath contain any special characters?
    No, it's the desktop.

    Are you trying to play in a virtual machine?
    No.

    Are you using any av software besides defender?
    No, and I have none installed.

    Check windows event viewer for anything that comes up after trying to start the launcher.

    b6014be3-3c97-4c4c-9ba7-1b19203ad4b2-image.png
    These two events show up right after attempting to run. The sources are ".NET Runtime" and "Application Error".
    I'm not going to include any other information in this reply, as I am unsure if there is any potentially vulnerable information in the details of the errors.

    If you do need the details, please let me know.

    Dss0undefined 1 Reply Last reply
    0
    • Dss0undefined Offline
      Dss0undefined Offline
      Dss0 Plutonium Staff
      replied to no rome on last edited by
      #4

      @no_rome said in Plutonium.exe does not run. First time setting up.:

      I'm not going to include any other information in this reply, as I am unsure if there is any potentially vulnerable information in the details of the errors.

      No there's not, apart from your windows username maybe so if that's your real name censor it.

      no romeundefined 1 Reply Last reply
      0
      • no romeundefined Offline
        no romeundefined Offline
        no rome Contributor
        replied to Dss0 on last edited by no rome
        #5

        Dss0

        The .NET Runtime error event reads as follows:

        Application: Plutonium.exe
        Framework Version: v4.0.30319
        Description: The process was terminated due to an unhandled exception.
        Exception Info: System.BadImageFormatException
           at System.Environment.GetResourceFromDefault(System.String)
           at System.Diagnostics.StackTrace.ToString(TraceFormat)
           at System.Exception.GetStackTrace(Boolean)
           at System.Exception.InternalPreserveStackTrace()
           at System.Security.Policy.PolicyLevel.GetBuiltInSet(System.String)
           at System.Security.PermissionSet.CreateSerialized(System.Object[], Boolean, Byte[] ByRef, System.Security.PermissionSet ByRef, System.Security.Permissions.HostProtectionResource, Boolean)
           at ControlzEx.Behaviors.WindowChromeBehavior..ctor()
           at MahApps.Metro.Controls.MetroWindow.InitializeWindowChromeBehavior()
           at MahApps.Metro.Controls.MetroWindow..ctor()
           at Plutonium.Updater.App.Windows.UpdateWindow..ctor(Plutonium.Updater.Core.Models.UpdaterInfo, System.String, Boolean, Boolean)
           at Plutonium.Updater.App.App+<Application_Startup>d__1.MoveNext()
           at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
           at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
           at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
           at System.Windows.Threading.DispatcherOperation.InvokeImpl()
           at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
           at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
           at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
           at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
           at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
           at System.Windows.Threading.DispatcherOperation.Invoke()
           at System.Windows.Threading.Dispatcher.ProcessQueue()
           at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
           at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
           at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
           at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
           at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
           at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
           at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
           at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
           at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
           at System.Windows.Application.RunDispatcher(System.Object)
           at System.Windows.Application.RunInternal(System.Windows.Window)
           at Plutonium.Updater.App.App.Main()
        

        The Application Error event reads as follows:

        Faulting application name: Plutonium.exe, version: 1.0.210.0, time stamp: 0xb95ed1a9
        Faulting module name: KERNELBASE.dll, version: 10.0.19041.1387, time stamp: 0x0b9a844a
        Exception code: 0xe0434352
        Fault offset: 0x0000000000034f69
        Faulting process id: 0xb7c
        Faulting application start time: 0x01d80a85b88b83dd
        Faulting application path: C:\Users\rome\Desktop\Plutonium.exe
        Faulting module path: C:\Windows\System32\KERNELBASE.dll
        Report Id: cec772b8-ce46-4485-ae3a-979b2028084d
        Faulting package full name: 
        Faulting package-relative application ID:
        

        I hope this helps.

        Dss0undefined 1 Reply Last reply
        0
        • Dss0undefined Offline
          Dss0undefined Offline
          Dss0 Plutonium Staff
          replied to no rome on last edited by
          #6

          @no_rome are you running a 32 bit version of windows by any chance?

          no romeundefined 1 Reply Last reply
          0
          • no romeundefined Offline
            no romeundefined Offline
            no rome Contributor
            replied to Dss0 on last edited by no rome
            #7

            Dss0 No, I'm running a 64-bit version.

            Unsure if this information is relevant, but this may help narrow down options:

            4949a39e-c84b-400b-910f-a0f3011371d3-image.png

            Resxtundefined Dss0undefined 2 Replies Last reply
            0
            • Resxtundefined Offline
              Resxtundefined Offline
              Resxt Plutonium Staff
              replied to no rome on last edited by
              #8

              @no_rome You seem to have an old version of Windows 10.
              Upgrading to the latest version will probably solve your issue
              https://www.microsoft.com/en-us/software-download/windows10

              1 Reply Last reply
              0
              • Dss0undefined Offline
                Dss0undefined Offline
                Dss0 Plutonium Staff
                replied to no rome on last edited by Dss0
                #9

                @no_rome ok.. i assume you installed the runtimes using the links in this post? https://forum.plutonium.pw/topic/6832/common-launcher-issues-solutions

                Could also try this:

                • open the start menu and search for "cmd"
                • run cmd as admin
                • execute the following command
                dism /online /cleanup-image /restorehealth
                
                • after dism has finished repairing your system restart your pc

                usually badimageexception is caused by running 64 bit software on a 32 bit system but that's not the case here, you're also running the latest version of win10 so that's fine. No idea really.

                Resxt nah build 19043 is version 21h2.

                no romeundefined 1 Reply Last reply
                0
                • no romeundefined Offline
                  no romeundefined Offline
                  no rome Contributor
                  replied to Dss0 on last edited by no rome
                  #10

                  Dss0

                  ok.. i assume you installed the runtimes using the links in this post? https://forum.plutonium.pw/topic/6832/common-launcher-issues-solutions

                  Yes.

                  dism /online /cleanup-image /restorehealth

                  This is what it told me.

                  5ab6b55d-9d22-4d59-8b42-f727b2d2578e-image.png

                  If attaching the log file would help, I can do that.

                  Dss0undefined 1 Reply Last reply
                  0
                  • Dss0undefined Offline
                    Dss0undefined Offline
                    Dss0 Plutonium Staff
                    replied to no rome on last edited by Dss0
                    #11

                    @no_rome yea attach it, that's not a good sign tho, this could point to corrupted system files. Try this:

                    chkdsk /offlinescanandfix
                    

                    if it asks you if you want to schedule the scan for the next restart type Y then restart your pc.

                    no romeundefined 1 Reply Last reply
                    0
                    • no romeundefined Offline
                      no romeundefined Offline
                      no rome Contributor
                      replied to Dss0 on last edited by
                      #12

                      Dss0 I know it isn't; honestly, I was fearing this outcome. About a month ago, I had to completely nuke my entire PC and boot a new untouched OS from a USB stick, deleting every partition that had been created on the system because I was having a similar problem regarding .NET Framework and a corrupted OS. The fact that this is happening again despite the fact that I basically nuked my last OS and rebuilt a completely new one is just exhausting to me.

                      Nevertheless, here's the log file:
                      First half: https://pastebin.com/Bj1FHjeG
                      Second half: https://pastebin.com/UzLeSH6j

                      I'll try that command and get back to you with the results.

                      1 Reply Last reply
                      0
                      • no romeundefined Offline
                        no romeundefined Offline
                        no rome Contributor
                        wrote on last edited by
                        #13

                        Reinstalled my entire OS instead. It was just too much work. Thank you Dss0 for the help.

                        1 Reply Last reply
                        0

                        • Login

                        • Don't have an account? Register

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Recent
                        • Tags
                        • Popular
                        • Users
                        • Groups
                        • Donate