You either have to delete it, and re-download it through the WoW Launcher. or run the World of Warcraft Repair Tool.
this may reset you patch no. but try running the repair.exe in your wow folder
In the directory that wow is located in, there is a file called repair.exe. run that file, it will scan wow and tell you what needs to be done. this is also how you revert it back to default settings if something messes up.
How to Fix file integrity violated Error
Realmlist.wtf is a file which is used to show you the official WoW servers.Yoi change this file to gain access to private servers. It is highly not recommended that you change this file as private servers are ILLEGAL.
The realmlist file should be in your <wowprogramfolder>\Data\enUS\ folder.
You can try to go into the program file and click on the WOW folder and then click on WOW FIX. It will check what you have with what you should have and fill in the missing pieces. Just remember depending on your computer this can take a while.
pay your bill.
go to your WoW folder, then Data/enGB (OR enUS) then open the file "realmlist.wtf" in notepad.
You can just delete the patch file once downloaded and installed by wow. You can not revert wow to a previous version because wow is auto-updating. Every client has the exact same version (for their OS).
Sharon Steuer has written: 'The Illustrator 10 Wow! book' -- subject(s): Adobe Illustrator (Computer file), Computer graphics 'The illustrator wow! book' -- subject(s): Adobe Illustrator (Computer file), Macintosh (Computer), Computer graphics, Programming 'The Adobe Illustrator CS3 Wow! Book (WOW!)' 'The illustrator 6 wow! book' -- subject(s): Adobe Illustrator (Computer file), Macintosh (Computer), Computer graphics, Programming 'The Adobe Illustrator CS4 wow! book' -- subject(s): Adobe Illustrator (Computer file), Computer graphics 'Arte Y Creatividad Con Photoshop/art And Creativity of Photoshop' 'The CorelDraw Wow! Book'
¿ wow this really helps ?
Yes and no. The dll file may be just misplaced, then yes. A defrag your hdd and that should fix it. If a dll file is corrupt, then no. You will have to find or repair the dll file yourself.