Hi Lpkh,
1. Are you using any freeserver?
Method 1:
I suggest you to follow these below provided steps and check if the issue gets fixed.
Step 1: Delete the Cache folder of World Of Warcraft.
a. Click on start button.
b. Click on computer. c. Click on program files. d. Click on World of Warcraft. e. Click on cache folder. f. Select all the files and click on delete.
Step 2: Try disabling the addons and check.
a. Click on start button.
b. Click on computer. c. Click on program files. d. Click on World of Warcraft. e. Click on Interface. f. Addons.
Step 3: Delete your WTF (World of Warcraft temporary folder) folder in the WOW folder.
a. Click on start button.
b. Click on computer. c. Click on program files. d. Click on World of Warcraft. e. Delete WoW Temporary Folder.
Method 2:
Try updating the display adapter drivers on your computer and check if the issue gets fixed.
Refer:
Update a driver for hardware that isn't working properly
http://windows.microsoft.com/en-us/windows7/Update-a-driver-for-hardware-that-isnt-working-properly
I suggest you to visit your manufacturer's website to download the latest display adapter drivers.
For more information:
Thanks and Regards:I. Suuresh Kumar - Microsoft Support. Visit our Microsoft Answers Feedback Forum and let us know what you think. Posted by
Winston
2 years ago
I downloaded Battle.net launcher to play the free weekend, I liked the game, so I went ahead and bought Origins Edition yesterday. Today, I tried starting Battle.net launcher and it returns a different error code every time I try to launch it:
The application encountered an unexpected error
I already tried:
If I do this I can open the client ONE more time, but if I decide to close it and open again, then the errors come back. How to fix this? It's really annoying, I want to play the game so bad. Appreciate any help! :(
SOLVED: I have two drives C (OS drive, SSD) and D (data drive, HDD). I usually install Steam, uPlay, Origin and games in general on D drive because it's larger. I did this for Battle.net launcher (installation on D drive) and this was the issue. I had to remove it and install on the C drive and then I just had to change the 'games folder' settings inside the client so my games reside on the D drive and every new installation goes to the D drive.
7 comments
I've had a Hyper-V running Windows Server 2008 for about two years. Today I did a Save on the VM in the Hyper-V Manager and then restarted my computer. When computer restarted I went to Start this VM and got the following error:
[Window Title] Virtual Machine Connection
[Main Instruction] The application encountered an error while attempting to change the state of 'WindowsServer2008'. Civ 5 mods enabled but not working.
[Content] 'WindowsServer2008' failed to restore.
Microsoft Video Monitor (Instance ID BA8735EF-E3A9-4F1B-BADD-DBF3A5909915): Failed to restore with Error 'Catastrophic failure'.
[Expanded Information] 'WindowsServer2008' failed to restore. (Virtual machine ID 07307F40-CA38-4780-A62B-CD873410948D)
'WindowsServer2008' Microsoft Video Monitor (Instance ID BA8735EF-E3A9-4F1B-BADD-DBF3A5909915): Failed to restore with Error 'Catastrophic failure' (0x8000FFFF). (Virtual machine ID 07307F40-CA38-4780-A62B-CD873410948D)
The Event Viewer had no additional error information and just repeated the above messages. I did not change any monitor or drivers on my system. I started up a different VM on my system that runs Win 8.1 and that came up with no problem.
What can I try to fix this?
Walter
Battlenet The Application Encountered An Unexpected Error Video
WalterWalter
3 Answers
The saved state is corrupted, in Hyper-V manager select the vm and delete saved state.
More details:
Juan BlancoJuan Blanco
I had this problem and in my case the solution was very simple. My HDD (where the virtual disk was stored) was full and I had to delete some files to get enough space to be able to start the VM. The error message that I got was super unhelpful, I had to go to Event Viewer and find some error code 0x80070070, Google it and then finally I found that it had something to do with disk space. Hyper-V should be able to just tell me that..
gakeragakera
I found out how to fix this. Apparently the .vhdsk was still good just the saved state was bad. In the Hyper-V Manager I created a new VM and in the Wizard create process I chose the option to use an existing .vhdsk and pointed it at mine. I connected to it and all was fine! I lost any unsaved data in applications that were open but that's nothing to thinking I lost the entire VM.
WalterWalter
Not the answer you're looking for? Browse other questions tagged windowswindows-server-2008hyper-v or ask your own question.Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |