Error at hooking api loadstringa dumping first 32 bytes rainbow six siege решение
For those hoping for a fix from Ubi this is the most recent update in my case. Seems they effectively given up:
Thank you for that update. At this time we don't have a report from the development team that this is a known issue.
So I will forward this up to the development team for further review. However, that is all that we can do at this time, as we have no further information.
Hopefully someone from the development team finally gets word of the issue. All customer support can do is follow a script to resolve known issues and can't investigate issues that need a developer to fix. I don't expect a fix until redstone 2 is officially released and they are forced to resolve the issue as people's OS get upgraded and people start experiencing the issue on a larger scale.
As an update I updated to teh new pre-release version of redstone 15002 170102-1700. Now instead of the error dialog the process just hangs without the error message. I suspect teh same issue but maybe now that the build is a pre-release version its being less verbose on errors that occur. Now when launching the game the process just hangs and nothing happens.
I just updated to version 15025 of Redstone and now the game will launch correctly
Solution
The firsat solution worked for me so hopefully one of these can help you guys
1. Disabling your background applications:
Go to the Start menu on your Desktop. Press the Windows key and the letter R at the same time.
Type in MSCONFIG and press Enter.
Go to the Startup tab, and click Open Task Manager.
For each Startup item in the Task Manager, select the item then click Disable.
Close Task Manager.
On the Startup tab of the System Configuration dialog box, click OK, then restart the computer.
Note: For Windows 7, you can simply click Disable All on the Startup tab within the System Configuration window.
2. Clearing your temporary files:
Go to the Start menu on your Desktop. Press the Windows key and the letter R at the same time.
Type in %TEMP% and press Enter.
Select All (Edit > Select All or Ctrl+A).
Click the Delete key.
Note: If you are using Windows 7, you will need to press Ctrl + A together to highlight the files. Once the files are highlighted, you will need to press the Delete key.
3. Make sure the drivers for your video card, sound card, motherboard and processor are up-to-date. Running 2 cards in SLI or running 2 screens can also cause issues. Deactivate SLI or unplug any additional screens you may be using. If you are overclocking, try running at the stock clock settings.
4. Make sure that any antivirus or firewall software on your system is disabled.
To troubleshoot this issue for you, I need two files from your system (Direct X and MS System Information). These files report information about system drivers for your video and sound cards, as well as other vital information about your computer hardware that will help me resolve your problem.
After installing DirectX, follow these steps:
If you receive an error when attempting to upload the MSINFO32 file stating that it is too large, you will need to compress it using either WinZip or WinRAR. Once received, we will examine your system info and get back to you as soon as we can with a possible solution to your problem.
Windows 10 Pro Insider Preview 14971.rs_prerelease.161111-1700.
GTX 1070 drivers 376.09. DirectX 12.
I had the same problem in Beta as others were that were also running the insider preview (redstone 2) version of Win 10.
Tom Clancy's The division launches fine still.
I posted the exact same issue a couple days ago also with several steps Ubi has had me try via a support ticket I opened. After several canned responses/generic troubleshooting suggestions failed they stopped responding and have not for a couple days now. You can find the thread here. If anything hopefully it will save you some time with Ubi if you open a case. Please reference my case number (in my post) if you have a case open as well.. maybe if a few of this report it they'll consider taking a look since all other instances of this issue I've found both on the forums, beta forums and reddit have gone unanswered.
Have you found a solution? Because i have the exact same problem
LoadStringA comes from C:\Windows\System32\user32.dll The offset for LoadStringA is different for Win 10 Restone 2(our insider build) vs Win 10 Redstone 1 (current version). I suspect they have code that checks the 'OS' and if it is 'Win 10' they use an offset that works for Redstone 1 but not Redstone 2. So when they try to hookinto a core os function (bad implementation decision on their side) with the wrong offset it fails. I think they need an additional check for Win 10 based on build number and use offsets that match the build of Win 10 if they want to try hooking into core OS files.
In Redstone 2 LoadStringA is located at offset 0x00031140
In Redstone 1 LoadStringA is located at offset 0x00032DF0
If they are trying to hook to the function by Ordinal that has also changed from 2095 to 2097.
Unfortunately until this gets escalated to an actual developer and now a CSR following some flow chart I don't expect a solution. Or Redstone 2 goes live in March and it gets more visibility and finally escalated up.
LoadStringA comes from C:\Windows\System32\user32.dll The offset for LoadStringA is different for Win 10 Restone 2(our insider build) vs Win 10 Redstone 1 (current version). I suspect they have code that checks the 'OS' and if it is 'Win 10' they use an offset that works for Redstone 1 but not Redstone 2. So when they try to hookinto a core os function (bad implementation decision on their side) with the wrong offset it fails. I think they need an additional check for Win 10 based on build number and use offsets that match the build of Win 10 if they want to try hooking into core OS files.
In Redstone 2 LoadStringA is located at offset 0x00031140
In Redstone 1 LoadStringA is located at offset 0x00032DF0
If they are trying to hook to the function by Ordinal that has also changed from 2095 to 2097.
Unfortunately until this gets escalated to an actual developer and now a CSR following some flow chart I don't expect a solution. Or Redstone 2 goes live in March and it gets more visibility and finally escalated up.
Windows 10 Pro Insider Preview 14971.rs_prerelease.161111-1700.
GTX 1070 drivers 376.09. DirectX 12.
I had the same problem in Beta as others were that were also running the insider preview (redstone 2) version of Win 10.
Tom Clancy's The division launches fine still.
I posted the exact same issue a couple days ago also with several steps Ubi has had me try via a support ticket I opened. After several canned responses/generic troubleshooting suggestions failed they stopped responding and have not for a couple days now. You can find the thread here. If anything hopefully it will save you some time with Ubi if you open a case. Please reference my case number (in my post) if you have a case open as well.. maybe if a few of this report it they'll consider taking a look since all other instances of this issue I've found both on the forums, beta forums and reddit have gone unanswered.
Have you found a solution? Because i have the exact same problem
LoadStringA comes from C:\Windows\System32\user32.dll The offset for LoadStringA is different for Win 10 Restone 2(our insider build) vs Win 10 Redstone 1 (current version). I suspect they have code that checks the 'OS' and if it is 'Win 10' they use an offset that works for Redstone 1 but not Redstone 2. So when they try to hookinto a core os function (bad implementation decision on their side) with the wrong offset it fails. I think they need an additional check for Win 10 based on build number and use offsets that match the build of Win 10 if they want to try hooking into core OS files.
In Redstone 2 LoadStringA is located at offset 0x00031140
In Redstone 1 LoadStringA is located at offset 0x00032DF0
If they are trying to hook to the function by Ordinal that has also changed from 2095 to 2097.
Unfortunately until this gets escalated to an actual developer and now a CSR following some flow chart I don't expect a solution. Or Redstone 2 goes live in March and it gets more visibility and finally escalated up.
LoadStringA comes from C:\Windows\System32\user32.dll The offset for LoadStringA is different for Win 10 Restone 2(our insider build) vs Win 10 Redstone 1 (current version). I suspect they have code that checks the 'OS' and if it is 'Win 10' they use an offset that works for Redstone 1 but not Redstone 2. So when they try to hookinto a core os function (bad implementation decision on their side) with the wrong offset it fails. I think they need an additional check for Win 10 based on build number and use offsets that match the build of Win 10 if they want to try hooking into core OS files.
In Redstone 2 LoadStringA is located at offset 0x00031140
In Redstone 1 LoadStringA is located at offset 0x00032DF0
If they are trying to hook to the function by Ordinal that has also changed from 2095 to 2097.
Unfortunately until this gets escalated to an actual developer and now a CSR following some flow chart I don't expect a solution. Or Redstone 2 goes live in March and it gets more visibility and finally escalated up.
13 мар. 2019 в 13:55Здравствуйте, столкнулся недавно с проблемой:
Error at hooking API "LoadStringA"
Dumbing first 32 bytes:
48 8B C4 48 89 58 08 48 89 68 10 48 89 70 20 4C
89 40 18 57 48 83 EC 40 41 8B F1 49 8B D8 33 ED
Кто знает решение, напишите (Целостность файлов проверял, стим писал что всё ок).
Hey there tyna F/\ek$$ep!
Support is available in English on the forum. However, have you tried verifying the game's files to try and resolve this issue:
I hope this helps! If not, please translate your reply and we will look further into it.
Читайте также: