Jump to content


Photo

Windower 4 itself runs, does nothing when trying to load PlayOnline


    7 replies to this topic

    #1 Kokonoe

    Kokonoe

      Newbie

    • Members
    • Pip
    • 6 posts

      Posted 13 November 2016 - 07:23 PM

      I'm using the Windows 10 insider build, and in the past on Windows 10, I use to be able to use Windower 4, but after many months later I decide to play the game again. Windower 4 itself runs fine, the moment I click to boot PlayOnline, it literally does nothing and closes out. No PlayOnline crash, no crashdump, no nothing.

      So far I've:

      1.
      Uninstalled and reinstalled FFXI.

      2.
      Checked my registry, and there's only the US registry, so there are no other regions involved and the locations/paths are correct.

      3.
      Tested PlayOnline and FFXI and they run perfectly without Windower.

      4.
      Tested with Windower 3, and it's able to boot PlayOnline, surprisingly.

      5.
      Closed out all programs except Windower 4 to no avail.

      6. 
      Set the Region to North America in Windower 4.

      So... I literally am clueless on to what's going on here. Any help would be greatly appreciated.

      PS: 
      Below is a video showing exactly what happens, however, something crazy happened when I was recording. I set the region to "North America" again, and for a brief moment PlayOnline actually ran! albeit it crashed right afterward, and there wasn't a crashdump in the Windower4 folder, unfortunately.



       



      #2 Kokonoe

      Kokonoe

        Newbie

      • Members
      • Pip
      • 6 posts

        Posted 14 November 2016 - 05:49 PM

        Used WinDbg on Windower 4 itself since I can't use it on PlayOnline for this and this is what it stated.

        (3670.3780): Break instruction exception - code 80000003 (first chance)
        *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\SYSTEM32\ntdll.dll - 
        *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\System32\KERNEL32.dll - 
        eax=0083a000 ebx=00000000 ecx=77cd3480 edx=77cd3480 esi=77cd3480 edi=77cd3480
        eip=77c9f4c0 esp=08f7f774 ebp=08f7f7a0 iopl=0         nv up ei pl zr na pe nc
        cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246
        ntdll!DbgBreakPoint:
        77c9f4c0 cc              int     3
        0:015> g
        (3670.3674): Unknown exception - code 0000071a (first chance)
        eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=00000000 edi=77d3e980
        eip=77c9d5fc esp=00aff544 ebp=00aff618 iopl=0         nv up ei pl nz na pe nc
        cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00200206
        ntdll!NtTerminateProcess+0xc:
        77c9d5fc c20800          ret     8
        


        #3 Kokonoe

        Kokonoe

          Newbie

        • Members
        • Pip
        • 6 posts

          Posted 14 November 2016 - 06:27 PM

          Excuse the triple post, but I believe I have some new information that might shed some light on this popular issue with Windower 4 and Windows 8/10 that might lead to a solution.

          New Info

          I noticed that if I rebooted my computer and immediately ran Windower 4 at startup, PlayOnline would actually run, but if I clicked on anything it would crash. Yet, if I never clicked a single thing, it would remain working and the little cursor would animate still and be fine, but when it became, I assume, the main window again, it would instantly crash.

          After it crashes, and you try to open Windower 4 again, it will just instantly crash, so it made it impossible to get a WinDbg log.

          So, by exploiting this reboot thing, I managed to snag a WinDbg log of PlayOnline after it is booted from Windower 4 and when I click on PlayOnline, so here are the results:
           

          (26a8.27dc): Break instruction exception - code 80000003 (first chance)
          *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\SYSTEM32\ntdll.dll - 
          *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\System32\KERNEL32.DLL - 
          eax=00373000 ebx=00000000 ecx=77273480 edx=77273480 esi=77273480 edi=77273480
          eip=7723f4c0 esp=0095ff54 ebp=0095ff80 iopl=0         nv up ei pl zr na pe nc
          cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246
          ntdll!DbgBreakPoint:
          7723f4c0 cc              int     3
          0:014> g
          ModLoad: 681e0000 68241000   C:\WINDOWS\SysWOW64\textinputframework.dll
          ModLoad: 670e0000 67168000   C:\WINDOWS\SysWOW64\CoreMessaging.dll
          ModLoad: 67170000 67379000   C:\WINDOWS\SysWOW64\CoreUIComponents.dll
          ModLoad: 73d00000 73d28000   C:\WINDOWS\SysWOW64\ntmarta.dll
          (26a8.26ac): Access violation - code c0000005 (first chance)
          First chance exceptions are reported before any exception handling.
          This exception may be expected and handled.
          *** WARNING: Unable to verify checksum for C:\Program Files (x86)\Windower4\Hook.dll
          *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Program Files (x86)\Windower4\Hook.dll - 
          eax=00000004 ebx=009c69c0 ecx=02884978 edx=00000000 esi=00000000 edi=00c3a978
          eip=026ffbf0 esp=0019be0c ebp=0019be0c iopl=0         nv up ei pl zr na pe nc
          cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
          Hook!zmq_stopwatch_stop+0xbd890:
          026ffbf0 0fb702          movzx   eax,word ptr [edx]       ds:002b:00000000=????
           
          

          What I'm taking from this is the following:

          1.
          There is something Windows 10 is potentially loading that causes a crash and it's why I can boot it temporarily at startup.
          2.
          Perhaps this is some kinda window issue because if I don't click on PlayOnline, it runs, but the second I do, it instantly crashes.
          3.
          The crash log states "*** WARNING: Unable to verify checksum for C:\Program Files (x86)\Windower4\Hook.dll" so I'm assuming the Hook is either the cause or partially to blame here.

          So I hope this helps you guys find a solution to this.


           



          #4 shorezone

          shorezone

            Newbie

          • Members
          • Pip
          • 1 posts

            Posted 19 November 2016 - 11:06 PM

            Hi there. I'm experiencing the same error since updating to Windows 10 build 14393.447.



            #5 Kokonoe

            Kokonoe

              Newbie

            • Members
            • Pip
            • 6 posts

              Posted 02 April 2017 - 06:16 PM

              As one final update to this, the only way I solved it was by reinstalling windows and disabling updates. I imagine Windower 10 just isn't compatible with preview builds of Windows 10, so do not install preview builds if you wish to use Windower. If you still want to use preview builds, google "Windower alternative" and there's another application out there that starts with the letter "A" that can work.



              #6 sdahlka

              sdahlka

                Advanced Member

              • Members
              • PipPipPip
              • 324 posts

                Posted 03 April 2017 - 02:54 AM

                are you running windower as admin

                and i do not mean just on the admin account but by right clicking one the windower link and selecting "Run as administrator"



                #7 laziale

                laziale

                  Member

                • Members
                • PipPip
                • 28 posts

                  Posted 04 April 2017 - 02:33 PM

                  for me pol and game launch but none plugs or add on work got "unexpected symbol" error message for each add on or plug trying to launch 



                  #8 IBHalliwell

                  IBHalliwell

                    Advanced Member

                  • Members
                  • PipPipPip
                  • 102 posts
                  • LocationBastok (Chicago)

                  Posted 04 April 2017 - 04:34 PM

                  Hi there. I'm experiencing the same error since updating to Windows 10 build 14393.447.

                   

                  According to WinVer, I'm on Windows 10 Version 1511 (OS Build 10586.839) and I do not see the problem.

                   

                  Thanks for the warning about 14393.447.  I noticed you posted in November 2016 and its now April 2017.  Are you still having the same issue?  Are you on the same OS build now?

                   

                  Thanks!






                  1 user(s) are reading this topic

                  0 members, 1 guests, 0 anonymous users