All I did was restart my PC now it says its not compatiable with my computer... its a 64 bit windows 7 I don't understand how after one restart makes it "not compatiable" with my verision of windows.

Windower not compatiable with Windows 7? Says I need 64 bit?
#1

Posted 13 March 2015 - 10:36 AM
#2

Posted 13 March 2015 - 10:51 AM
This is the first time I've ever heard of this. Can you post a screenshot of the error window?
#3

Posted 13 March 2015 - 11:07 AM
I noticed I have 24 important updates not installed which Im assuming maybe its a update for the netframework but gonna see what happens after that. I avoided the update cause I triobox... and it gave me a error when i did 3 screens only. So updating to see what happens and I forgot how do I do a screenshot for windows 7?
#4

Posted 13 March 2015 - 12:41 PM
So after updating and reinstalling same message and now after it states "this is not a 64 bit program and is not compatiable with my windows verison" (which is windows 7 64 bit) the shortcut disappears...
#5

Posted 13 March 2015 - 12:58 PM
Now it opens windower but once it starts lauching the playeronline before it can show it it crashes sstating "WIndower launcher has stopped responding. A problem caused the program stop working correctly
windows will close the program.." OVer a fucking restart god this is getting old.
3/13/2015 6:55:50 AM
---------------------------------------------------------------------
System.TimeoutException: The operation has timed out.
at #=qy70dAO9QhgENx99v620sV10rm3SOXZM3R10$qiklAtE=.#=q5OhMqDV8FaoasiZjAiyXWQ==(#=qTqKCSC0u8NAekF9KIFAfBg8qHu2K8CTWhMeLWvZ0Q90= #=qbylrgTuzL6EAogTxgivjJg==, String #=qRdrbBulKP0eqnAsOwFc6sA==, #=qiOicJhOA_9ZSCxawyLGnXg== #=quFDE_zdA1wnC1K4rWCNk7Q==, TimeSpan #=qiaQrUrAemtT$fBdnZn_qXw==)
at #=qy70dAO9QhgENx99v620sV10rm3SOXZM3R10$qiklAtE=.#=qBwp9l1SBn_JZ17USRwdk8Q==(String #=qi3lskcH2JoasUfOkcYrlOQ==, #=qL96jFcosDWJLpZnWSG2aiZsuHZARO2lCBkJO1WR8cDM= #=qvRynItAU2jUmFrMf3f0DUA==, TimeSpan #=q7Zwtz9MGbOVBfG1uHbnZvA==)
at #=qy70dAO9QhgENx99v620sV10rm3SOXZM3R10$qiklAtE=.#=q9O5DNPRkCZb5PC53vGvTCQ==(String #=qKs4bh1EndAOZiDI7iFaE1g==, #=qL96jFcosDWJLpZnWSG2aiZsuHZARO2lCBkJO1WR8cDM= #=q1qfrVdTypJELo3ZtMfLOtw==)
at #=qScHB9gQmT6r4ibODeedMuo$czA8EY1jL1a2BbIcwPuE=.#=qkGdMkB58AB_Q1OG4U$XHsg==()
at #=q4w9QFsTFa4BU8xF1yRAlgFJ1fQ1hntOmna8SPclpjrc=.#=qFc$Ip$hBMR$aMSE2M6ewrg==(#=qGPj1PfHTYqH$x9fq0oD8zg== #=qdhmJiRU$QCqMK0KRGWRoUA==)
at #=qGPj1PfHTYqH$x9fq0oD8zg==.#=qEfxG_jNs7XH8fLqex6ATHg==()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
=====================================================================
#6

Posted 13 March 2015 - 01:16 PM
The error log indicates that the launch attempt timed out. After attempting to inject the Windower hook dll into the PlayOnline Viewer process, the launcher waits for 30 seconds for the dll to notify the launcher that the injection was successful. If after that time has elapsed, it has still not received the notification, it aborts the launch, kills PlayOnline Viewer, and then forces itself to crash so that a crash log is written.
That's what's happening, as for why it's happening or what caused it to suddenly start I can't say. You may want to try checking if your anti-virus software is blocking Windower from injecting itself.
#7

Posted 13 March 2015 - 01:29 PM
Turned off antivirus and windows defender and checked settings POL and windower now are accepted by it and same error.. all of this over a restart of the PC I don't get it
#8

Posted 13 March 2015 - 01:38 PM
Tried new user accoutn and got this information:
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: windower.exe
Problem Signature 02: 4.0.4820.31935
Problem Signature 03: 51410159
Problem Signature 04: Windower
Problem Signature 05: 4.0.4820.31935
Problem Signature 06: 51410159
Problem Signature 07: 240
Problem Signature 08: 199
Problem Signature 09: System.TimeoutException
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft....88&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
#9

Posted 13 March 2015 - 02:57 PM
Restored from a few days ago... works fine now but of course no windows updates have to do them again which I wont I guess this seemed to happen after restarting and installing updates for windows 7
#10

Posted 15 March 2015 - 05:23 PM
I have been having the same issue on windows 7 64-bit. Worked fine last night, and this morning it says...
"Unsupported 16-Bit application" and says that the program or feature cannot start or run due to incompatibility issues with 64-bit versions of Windows. Please contact the software vendor to ask if a 64-bit Windows compatible version is available."
I run FFXI on WIndows 7 64bit pro and it was running perfectly until i installed Trend Micro....
Any help would be greatly appreciated!
Thanks!
#11

Posted 15 March 2015 - 05:51 PM
I'm having the same issue! I'm trying different things, but nothing fixes it yet!
#12

Posted 15 March 2015 - 06:03 PM
Which antivirus do you guys run on your PC?
#13

Posted 15 March 2015 - 06:17 PM
Trend Micro.
I'm coming to the conclusion that there was a Windower patch overnight that's messed this up. I restored my system to earlier this week, and it started opening Windower (Which was an improvement on earlier), then when it started doing the normal downloads the error popped up again. I'm hoping I don't have to end up downgrading to 32 bit Windows just to be able to play on dual box again.....
#14

Posted 15 March 2015 - 06:29 PM
Yeah - so Trend Micro isn't the problem right? One of the reasons why I switched to Trend from BitDefender was that it would block all transfers from POL to Windower.
Really hope this is resolved quickly...
#15

Posted 15 March 2015 - 06:34 PM
Pretty sure it's unrelated. I shut down Trend Micro and it still isn't working. I've always run TM, and never had this problem.
#16

Posted 15 March 2015 - 08:17 PM
Uninstalled Windower 4.0 and playing in FFXI windowed mode for now until there is a solution..
#17

Posted 15 March 2015 - 09:37 PM
same, but I don't think I can dual box like that.
#18

Posted 15 March 2015 - 10:32 PM
I adjusted the version so it won't overwrite the old file anymore. If you copy it in now it should work again. I don't have time to look into this error right now, but I'll do it tomorrow when I get a free minute or two, but I'll be really busy the next three days, so no promises.
#19

Posted 16 March 2015 - 12:59 AM
Sorry I'm new here, I didn't have a problem with Windower last night, today I can't seem to run it at all I checked crash report and I got this:
3/15/2015 6:52:52 PM
---------------------------------------------------------------------
System.ComponentModel.Win32Exception (0x80004005): The file or directory is corrupted and unreadable
at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at #=qq9HZxRMNaRmFXeeS_h$SOKqLoGbGZ1w1939mPtPjLT4=.#=q9hPyUWnAfbgTxvae8HX$7Q==()
at #=qwrZ0sKWfVuSrbsrEe$sq2ikYRakTupw24tqRYOrFtO4=.#=qnQCMKMqRLmsGND5_yA3M5Q==()
at #=qAlk$Mw_tywKjs9rd7cyoVByKGVe3vaaXeS_LGtl1hBE=.#=qfyJ2oWactrEI0jMMW5DrEA==(#=qmhNvAyztrFon0QQMItVoEw== #=q$_uA1omHXJgXxHzgfPGREA==)
at #=qmhNvAyztrFon0QQMItVoEw==.#=qav9FVComJWu2k_c7i_yB0A==()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
`````````````````````````````````````````````````````````````````````
You said you overwrote version, if that were to fix my problem where could I DL the new one? Thanks and sorry again.
#20

Posted 16 March 2015 - 01:51 AM
Thought Id chime in as well. I'm having the same problem.
Important note = I'm using Trend Micro.
When the problem happened, I didn't restart my pc. All I did was log out of the game to fix a bug, and log back in, and BOOM. I got the Wrong Version of Windowers Error 64 32 bit thing.
Here is a screen shot. I only got that second message before I uninstalled windower. I never saw it again with any of the new installs, which I tried reinstalling Windower 4 a good amount hehe.
http://i.imgur.com/7reBTJq.jpg?1
Things I tried:
Restarted PC
Reinstalled Windower (about 100 times :3)
Repair and reinstall multiple different types of frame work
Messed around in Windower properties for a good while.
Tried to do a system restore 4 days earlier to when Windower was working. (Really thought this one would work T_T)
Turned off all firewalls + Trend Micro.
A mix of other things. T_T
Thanks for listening and helping us with this issue, I understand fully how anyone can be busy and stuff, so get to it when you can, thanks again~
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users