Unable to identify version with Windows XP

General Discussion
So i just finished my school / studies and i loved D2 back when it was first launched decades ago...

so i decided to get D2Lod on my PC again..

5/29/16 is around when i reg'd my d2 + d2lod digital copies

so i dl and patched up to 1.14b by default and was playing fine till a week ago when they had us download patch 1.14d... like da fk.

i know and read on forums and see lots and lots of people have this same issue..

ever since then i contacted blizzard CS team and they gave me instructions / solutions which none of them had any success to the unable to identify version app...

so i spent around $20 for a classic game and we get cut off due to this patch??

since my cd / discs are no longer with me...

good job boys...!
maybe they will fix this issue soon who know, best wishes to you Guess
Not sure i understand your problem, are you saying you can'T download the latest patch? There is a download link to the installer, download it and install it from there, it worked for me

http://us.battle.net/en/forum/topic/20744104282
odd... no issues here really. I don't think I've ever not been able to get on diablo 2 ever... not even once been unable to patch since d2 started. Try the stand alone patch if the in game update doesnt work. or fully reinstally the game.
06/12/2016 04:20 PMPosted by Drayen
Not sure i understand your problem, are you saying you can'T download the latest patch? There is a download link to the installer, download it and install it from there, it worked for me

http://us.battle.net/en/forum/topic/20744104282

not sure what problem or forum u looking at lol. did u read?

i said i tried all the solutions the blizzard cs team / tech specialist asked me lol.

sending my OS specs & long list of trouble shoots they suggested...
i used manual & auto patch to no prevail

unless this patch specifically targets to lock out Win XP users as stated by other users in that other topic.. .. then its the dev's problem...

i dont want to / think its entirely necessary to buy a new PC with Win 10 just for D2.. since all my other games i play have no problem what so ever...
06/12/2016 03:37 PMPosted by Guess
so i dl and patched up to 1.14b by default and was playing fine till a week ago when they had us download patch 1.14d... like da fk.

i know and read on forums and see lots and lots of people have this same issue..


06/12/2016 07:35 PMPosted by Guess
not sure what problem or forum u looking at lol. did u read?

i said i tried all the solutions the blizzard cs team / tech specialist asked me lol.


You seem to have a problem with the newest patch. Like Deyan said, you didn't specify what kind of problem. I only figured out, that you are using Win XP. Try to explain it in detail, then maybe a customer support can help you and everyone else with the same problem.
But what exactly is your problem? You are just saying you have a problem and that the solutions aren't working but you didn't tell us what exactly is the issue you're having.
Morning,

Diablo II 1.14d should work as intended on Windows XP. if you are having problems, let us know what's going on in detail and we can try and see what the problem is.

Where is the game failing? Is it when you try to log into Battle.net? What does it say? Is there an error? a crash?

Any specifics and I can try and help as much as I can. If I can't for whatever reason, we can direct you do the support forum and someone will spend time figuring out what's wrong.
06/13/2016 10:55 AMPosted by Clásico
Morning,

Diablo II 1.14d should work as intended on Windows XP. if you are having problems, let us know what's going on in detail and we can try and see what the problem is.

Where is the game failing? Is it when you try to log into Battle.net? What does it say? Is there an error? a crash?

Any specifics and I can try and help as much as I can. If I can't for whatever reason, we can direct you do the support forum and someone will spend time figuring out what's wrong.

OP is receiving the Unable to Identify Version error which occurs when D2 calls CheckRevision.
06/13/2016 10:35 AMPosted by OShogun
But what exactly is your problem? You are just saying you have a problem and that the solutions aren't working but you didn't tell us what exactly is the issue you're having.


i did state the problem.. you probably just missed it cuz i didnt use bold
ever since then i contacted blizzard CS team and they gave me instructions / solutions which none of them had any success to the unable to identify version app...
06/13/2016 10:55 AMPosted by Clásico
Morning,

Diablo II 1.14d should work as intended on Windows XP. if you are having problems, let us know what's going on in detail and we can try and see what the problem is.

Where is the game failing? Is it when you try to log into Battle.net? What does it say? Is there an error? a crash?

Any specifics and I can try and help as much as I can. If I can't for whatever reason, we can direct you do the support forum and someone will spend time figuring out what's wrong.

Unable to Identify Version
06/13/2016 11:12 PMPosted by Guess
06/13/2016 10:35 AMPosted by OShogun
But what exactly is your problem? You are just saying you have a problem and that the solutions aren't working but you didn't tell us what exactly is the issue you're having.


i did state the problem.. you probably just missed it cuz i didnt use bold
ever since then i contacted blizzard CS team and they gave me instructions / solutions which none of them had any success to the unable to identify version app...


You are correct about stating your problem about the "Unable to Identify Version Application" issue but you were very vague when describing any solutions you may have tried to fix it. Simply stating that you contacted the Blizzard CS Team and following their instructions is not detail of what you have done.

06/12/2016 07:35 PMPosted by Guess


i said i tried all the solutions the blizzard cs team / tech specialist asked me lol.

sending my OS specs & long list of trouble shoots they suggested...
i used manual & auto patch to no prevail

unless this patch specifically targets to lock out Win XP users as stated by other users in that other topic.. .. then its the dev's problem...

i dont want to / think its entirely necessary to buy a new PC with Win 10 just for D2.. since all my other games i play have no problem what so ever...


All you said here was that you sent PC Specs & a long list of troubleshooting they suggested. The question is...what exactly were those troubleshooting steps you have taken? Furthermore, there is a support thread which was created about this issue 6 days ago and it's still not solved yet. You aren't the only one experiencing this same issue as many have already explained here.

http://us.battle.net/en/forum/topic/20745235089

I have a feeling that there isn't an answer to this solution yet which is why they haven't responded yet. I know this is frustrating but the only thing at this point I think that can be done is to be patient and hope Blizzard solves it soon. Best of luck.
06/14/2016 11:11 AMPosted by Moppi
Got this error since I had moved my d2 files from program files (x86) to desktop. I moved files back to program files (86), downloaded LoD patch from https://eu.battle.net/support/en/article/classic-game-patches and moved it inside d2 folder. Then running the patch as an administrator did the trick for me.


This solution seemed to have worked for someone having the same issue, you might want to give it a shot if you haven't already.
Try to manually download and install the patch.
oh yea a fortune 500 company duped you into spending 20 bucks.... seems legit.
I had solved this trouble on XP Home edition SP 3.
You need to right click on game shortcut and choose "Run as...", then choose bottom "Run as User" and fill in blanks with Administrator user data. You may need to change user settings in control panel by setting any password to administrator account - then you just try again to "Run as..." game shortcut, windows will remember it and choose it next time. All you have do after all patches and restarting system is delete password from user data and it will work correctly.


Another user just found a solution to this same problem you guys are having, hope this helps!

Join the Conversation

Return to Forum