Обновлено: 09.02.2023
2 мая. 2020 в 20:42
So anyway last night I was downloading some mods, and today I was going to play but then the game won’t launch. Vortex got an error saying exactly this, word for word: ‘Last time you ran the game, one or more script extender plugins failed to load. This normally happens when you try to load mods that are not compatible with the script extender. To fix this problem you can check for an update on the mod page or disable the mod until it is updated.
Error(s) reported: StorageUtil.dll (Campfire — Complete Camping System 1.11): not a valid dll (code 193)
Now I know for a fact that mod doesn’t need an update, so I did the only logical thing and disabled it, still no dice. So I did some research, a lot of people were saying to try a variety of different things, none of which helped (although some of the tips did put me a step in the right direction) however, one person said that installing mods made for the base 32 bit version of Skyrim won’t work with the 64 bit Skyrim SE, and indeed last night I did install mods made for the 32 bit version, so it sounds obvious right? Disable those mods, here’s where the problem lies, I have no way of knowing what those mods are, I could go back and check the websites, one by one, but with nearly 200 mods installed, that would take forever and I’m not willing to do that. There has to be an easier way, is there any way to check if a mod was made for Skyrim or Skyrim SE? Please help because I’m not willing to check every single website one by one, especially if it may not even fix the problem.
Follow the instructions, which are to update the mods in question so that they will work with the version of SKSE64 that you’re using.
l0udXD
I’ve been having trouble with this issue for a long time how can i fix this?
Attached Files
AugustaCalidia
Mayor of Talos Plaza
Follow the instructions, which are to update the mods in question so that they will work with the version of SKSE64 that you’re using.
Vvandemarr
i have this problem how tyo fix it. extratools .dll (manually installed) not a valid dll (code 193)
chip594
Follow the instructions, which are to update the mods in question so that they will work with the version of SKSE64 that you’re using.
I tried that, tried doing a quick update check, full check, even checking manually. They’re all updated. I took a screenshot:
Edited by chip594, 22 May 2020 — 01:36 PM.
AugustaCalidia
Mayor of Talos Plaza
What happens if you just click «Ignore»?
GreenStarRiot
Pickysaurus
GreenStarRiot
Kourtana
Im having a similar issue as well, except it is for these plugins:
These plugins also causes all animations to fail and everyone is at the stiff t-pose. I believe this may have something to do with FNIS based mods, but im unsure which one is causing it.
If you need my load order, I am more than happy to provide when asked!
horacio6siix
(1) RECOMMENDED: Completely remove all files and uninstall any previous installations of SSE Engine Fixes prior to starting.
(4) DO a fresh download, install and enable of Part 1 of SSE Engine Fixes with your mod manager. EngineFixes.ini has been replaced with EngineFixes.toml in 5.3.3+. Open the UTF-8 encoded .toml file in Notepad to make your setting changes. You can delete the old EngineFixes.ini.
(5) DO NOT install Part 2 of SSE Engine Fixes with your mod manager. Download it manually and EXTRACT the Part 2 zip, then copy and paste the 3 dll files from there directly into /steamapps/common/Skyrim Special Edition/. DO NOT simply place the zip file in that directory. DO NOT create a folder with the 3 files in that directory. DO NOT place the extracted files in your /Data directory.
OPTIONAL: If you are using Vortex, you can download and install Part 2 using the Mod Manager Download, but before deploying, double click the item in Vortex and change the Mod Type to dinput. Then enable/deploy Part 2.
DO NOT RENAME your skse64 executables. If you have already done so, you will need to CHANGE THE FILE NAMES BACK to the original skse executable names. That means skse64_loader.exe and SkryimSE.exe. Skyrim.exe and adding an INI, as several obsolete guides tell you to do to get skse launching from Steam, WILL NOT WORK. SSE Engine Fixes needs the original skse64_loader.exe and SkyrimSE.exe file names and files.
If you want to launch from Steam, add skse64_loader.exe as a Non-Steam Game. If Steam is open you can also launch skse64_loader.exe from a shortcut or from the mod manager and still get achievements in your Steam SSE Library and the overlay. The original Steam SSE page will always execute the standard launcher, but you can still see your achievements and screenshots there if you launch via skse64 using one of these other methods.
edit: dont download this s***, even after uninstalling it, the game wont load the menu anymore.
just because you cant get a product to work doesnt mean the product is faulted
Strange thing is, this patch fixes the functionality of the original mod, but the error message persists. Per the ‘delete the .json file’ in the description, no. I did not find any .json file in the directory of this patch.
The VR and SE patch released by the author fixes the error message. However, I had to reconfig the MCM menu setting everytime I load, quite troublesome actually, and sometimes the lantern is invisible while the light is not.
Any idea to help me resolve?
If you tried the mod and it didn’t work, check this one out.
Chesko’s Wearable Lanterns — SE and VR Patch <— This mod actually fixed it for me.
- supporter
- 1,751 posts
- 16 kudos
Thanks for this recommendation as it fixed the error I was getting. Wonder if LOOT team will update their message for it.
ILoveFluttershy wrote: ^^^^^^^^^^This mod right here is the real fix! ^^^^^^^^^^
HippeusOmega wrote: Thanks for this recommendation as it fixed the error I was getting. Wonder if LOOT team will update their message for it.
You need both mods. This one fixes the MCM menu, the linked one fixes the error code when you load a save.
- supporter
- 21 posts
- 1 kudos
EDITED: I’m getting error 193 thrown up in SKSE due to problems with storage utility.
Also not getting any of the meters or text to display when I have a lantern. This mod needs an update where the storage util is properly addressed.
Don’t use this mod. Ignore LOOT message to use this mod. Instead, follow below recommendation, install Wearable Lanterns, then install Chesko’s Wearable Lanterns — SE and VR Patch. Seems to work perfectly.
You should also have PapyrusUtil SE towards the end of your load order, after the above mods.
I agree, I get the same error, at least in VR. I’m uninstalling.
Ok, error occurs in skse64.log. But I didn´t have any problems with this Mod/Fix in game. MCM works perfect, no errors ingame, saves configuration and so on.
Hope this helped.
Your solution works! Everyone, just follow the advice by aristotle99 on installing Chesko’s Wearable Lanterns — SE and VR Patch.
- premium
- 1,175 posts
- 13 kudos
I FIXED IT! VR USERS MUST READ:
If you have the issue where your lantern does not light up at all when equipped or doing anything other
than dropping it, the problem is the brightness setting is set to 0 by
default. No matter what you do you will NOT see anything unless you
change the brightness setting within the MCM menu.
But the issue is you cant control menus with your controller to make that setting so
you are screwed. Unless you download THIS MOD:
VR Menu Mouse Fix
It enables a cursor like in PC skyrim where you can use your controller to
select menus like you would with a mouse. Once installed, go to the
Wearable Lanterns MCM menu and use the CURSOR with the new mod to select
values. You can use trigger to act as a mouse left-click and grab to
exit or save the changes.
All other settings work as well but there is the issue with Wearable Lanterns in general that it sometimes
resets your saved profile. NO WORRIES! All you really care about is the
brightness setting for it to just work. Of course using oil and
automatic mode is nice but hey, now you can see!
I spent a few days trying to figure this out and had to come back, this mod is a must in order to get this working.
So yea, Vortex reports the error, to the effect that «last time you loaded the game» SKSE reported the error. Vortex also gives you the option to ignore the error and dismiss the message. Though even if you do, it will still report the error again next time you run the game and start Vortex again.
(I install games on my D: drive.)
But, the error is reported by Vortex AFTER you’ve already loaded the game and see that the Wearable Lanterns MCM menu is fixed.
The suggestion to delete the StorageUtil.dll works. Personally, I just renamed it to StorageUtil.dll.testdelete in case it broke something and I had to put it back.
So after you install the patch, run the game and see the menu is fixed, you can go ahead and delete (or rename) that file. After that, the error is no longer logged by SKSE. (For all I know, you could install the patch and then delete the StorageUtil.dll before you ever ran the game and the menu would be fixed. Dunno, didn’t try it. I didn’t know about the error until after I’d already run the game and saw the menu was fixed.)
So IF the menu is fixed and you then delete the StorageUtil.dll, the menu stays fixed.
THANKS! I think this worked for me, I’m no longer receiving the 193 error code on Vortex.
Читайте также:
- Star wars jedi fallen order как поменять язык
- Lord of the rings battle for middle earth 2 вылетает
- Quantum break вылетает при просмотре сериала
- Dark souls 1 системные требования
- Сталкер дарк патч как установить
Skyrim SE Error 193 is reported by many gamers, after installing the mods in the Skyrim SE. Whereas for some users the error appears when they try to mod the Skyrim SE installation.
And as a result, they are unable to play the Skyrim SE, on their Windows system. The error is not limited to any particular Windows version it is seen on Windows 7, 8.1, and 10 OS.
The SE Error 193 appears with a long error message including the troubleshooting solutions to fix it, which isn’t very effective in solving the error for many users.
The main reason responsible for the error is installing the incompatible mods of Skyrim SE. For example, the mod designed for the 32-bit Skyrim version will not run in the 64-bit system of Skyrim SE.
However, after investigating we find out there are other reasons as well that cause the error code 193. So, below have a look at some of the possible culprits and then follow the potential fixes to get past the error on your Windows system.
What Causes Error 193 in Skyrim SE?
- Outdated software for extraction: The outdated extraction software or utilities corrupt some specific mod files during the process of extraction of files. This problem can be fixed by switching to advanced software like 7 ZIP instead of using old extraction tools like WinRar or WinZip that potentially corrupt the mod files.
- Missing administrative rights: If you install mods without admin access to make suitable modifications in the core program and its dependencies, this error code may pop up. In this scenario, you have to force the mode organizer utility to open with admin access to make desirable modifications for the smooth functioning of programs.
After a lot of stretch and stroll, we facilitate a detailed list of possible solutions that help you solve error 193 Skyrim SE.
How Do I Fix Skyrim SE Error 193 in Windows?
Trick 1 – Switch to different Extraction software
As said above the error can occur due to the incompatibility of unpacking software used to extract contents from Zip files.
So, check if you used the old version of WinRar or WinZip software for extracting the content of the Mod then switch to different extracting software
You download advanced extraction software like 7 Zip for your machine to stop the corruption of files.
Follow the steps to use it:
- Open the official website of 7 Zip in your default browser and download the latest edition of the tool compatible with your PC. There will be a range of tools for 32 bit and 64 bit as well as for AMD processors.
- After completing the download, double click on the installer, install the tool, and reboot your machine.
- Now pick out the mod files of Skyrim SE, right-click on it, and select option 7 Zip then click Extract Files (or Extract Here).
- Complete the extraction process simply by the following screen prompts and install the mod.
Check if the error Skyrim SE Error 193 has been resolved or not.
Trick 2 – Run Mod Launcher as Administrator
If the mod launcher does not have admin access, which you’re trying to install, then this can cause the error. If this case applies to you, then in this case you need to force your mod launcher app to run with admin access. To give admin access to your mod launcher, follow the below-mentioned steps.
- Go to the Mod launcher icon and right-click on it to open the context menu.
- Now choose the option Run as Administrator from the dropdown context menu.
Hope this works for you to fix Skyrim not a valid DLL Code 193 but if still seeing the error then head to the next possible fix.
Trick 3 – Disable Windows Defender Firewall & Antivirus
In some cases, few users claimed that this error could be solved by turning off the Windows Defender Firewall on their Windows 10 system. Sometimes, defenders may hinder the process and block the mod from running.
So here it is suggested to temporarily disable it and see if this works in your case.
- Open control panel.
- Now open the Systems and Security option and go to Windows Defender Firewall or (Windows Firewall for an earlier version)
- On the right side click on the option Turn Windows Defender Firewall on or off
- Then click on the checkbox to Turn off Windows Defender for public and private network
- Restart your system and check if this works for you
However, if you still see the error then it is advised to Turn on the Windows Defender Firewall and check if you are running the 3rd party antivirus then disable it.
There is a possibility that the antivirus program installed on your system conflicts with the mods and stops it from functioning properly.
To disable the antivirus program right-click on the antivirus icon in the taskbar and choose Disable Virus protection option
Now launch Skyrim and check if the error is fixed, if disabling the antivirus works for you to solve the problem then contact the antivirus support center for help or switch to a different security program.
Recommended Solution to Boost the Gameplay Experience on Windows
Many players encounter issues like game crashing, lagging, or stuttering when playing the game then optimize your gaming performance by running Game Booster.
This boosts the game by optimizing the system resources and offers better gameplay. Not only this, but it also fixes common game problems like lagging and low FPS issues.
Get Game Booster, to Optimize your Game Performance
Conclusion:
Here my job is done..!
I hope now the Error 193 in Skyrim SE will be fixed in your case and you are able to get use mod in your Skyrim SE.
If you haven’t tried the solutions yet then and feel free to follow them accordingly.
And as you are done fixing the error then read our guide to find out the best Skyrim Mods you can install to get the best gaming experience.
Moreover, it is suggested to scan your Windows system with the PC Repair Tool. As sometimes due to PC internal problems and glitches you start seeing various errors while playing games. This is an advanced tool and capable to solve various PC stubborn errors and issues.
If you have any queries or comment then feel free to share with us on our Facebook page, and do like and share button the article.
Good Luck..!
Hardeep has always been a Windows lover ever since she got her hands on her first Windows XP PC. She has always been enthusiastic about technological stuff, especially Artificial Intelligence (AI) computing. Before joining PC Error Fix, she worked as a freelancer and worked on numerous technical projects.
I’m testing your tutorial on the wiki. I successfully built the solution in visual studio 2017, then placed the DLL in E:Program Files (x86)SteamsteamappscommonSkyrim Special EditionDataskseplugins
, compiled the psc file and everything. However, SKSE fails to load the DLL:
SKSE64 runtime: initialize (version = 2.0.7 01050270 01D3EACC0B0AE4D2, os = 6.2 (9200)) imagebase = 00007FF6CF770000 reloc mgr imagebase = 00007FF6CF770000 config path = E:Program Files (x86)SteamsteamappscommonSkyrim Special EditionDataSKSEskse.ini plugin directory = E:Program Files (x86)SteamsteamappscommonSkyrim Special EditionDataSKSEPlugins checking plugin E:Program Files (x86)SteamsteamappscommonSkyrim Special EditionDataSKSEPlugins\plugin_example.dll couldn't load plugin E:Program Files (x86)SteamsteamappscommonSkyrim Special EditionDataSKSEPlugins\plugin_example.dll (Error 193) dispatch message (0) to plugin listeners no listeners registered dispatch message (1) to plugin listeners no listeners registered init complete hooked dinput dispatch message (6) to plugin listeners no listeners registered dispatch message (8) to plugin listeners no listeners registered save name is Quicksave0_497A45B9_1_4C697A_WhiterunBreezehome_000448_20180513145834_13_1 full save path: C:UsersuserDocumentsMy GamesSkyrim Special EditionSaves\Quicksave0_497A45B9_1_4C697A_WhiterunBreezehome_000448_20180513145834_13_1.skse dispatch message (2) to plugin listeners no listeners registered loading co-save Loading mod list: (0 -> 0) Skyrim.esm (1 -> 1) Update.esm (2 -> 2) Dawnguard.esm (3 -> 3) HearthFires.esm (4 -> 4) Dragonborn.esm (5 -> 5) VibHub.esp Loading light mod list: Loading menu open/close event registrations... Loading key input event registrations... Loading control input event registrations... Loading mod callback event registrations... Loading crosshair ref event registrations... Loading camera event registrations... Loading actor action event registrations... Loading NiNode update event registrations... Loading SKSEPersistentObjectStorage data... Loading SKSEDelayFunctorManager data... dispatch message (3) to plugin listeners no listeners registered cleared save path
Any idea what might cause this?
Причин появления несколько: неполная установка, повреждение реестра из-за изменения (установки или удаления), вредоносное ПО и т.д.
Как исправить?
Просканируйте ПК на вирусы вредоносное ПО.
Есть вероятность, что проблема связана с заражением компьютера. Вирусы повреждают или удаляют файлы. Поэтому очистка, вероятно, решит возникшую проблему.
Очистите систему от временных документов и папок.
Как запустить очистку диска в Виндовс XP, Vista, 7, 8 и 10?
- Нажимаем Winkey + R.
- Печатаем «cleanmgr» -> Enter.
- Откроется диалоговое окно «очистка диска», содержащее флажки. В большинстве, категория «временные файлы» занимает большую часть.
- Установите флажки напротив не использующихся категорий и примените.
- Поставьте автоматическое обновление драйверов устройств.
Ошибки 193 иногда связаны с повреждением или устареванием драйверов
- Запустите sysdm.cpl. Для этого используйте кнопки «Winkey + R», вбейте «sysdm.cpl» в командной строке и тапните Enter.
- В окне «свойства системы» кликните вкладку «оборудование».
- В «параметрах установки устройств» проверьте настройку автоматического обновления.
- На той же вкладке найдите диспетчер устройств.
- Не установленные или поврежденные драйверы обозначаются желтым знаком восклицания.
- Обновите автоматически или вручную.
Используйте «восстановление системы Виндовс» для отмены последних изменений.
Это вернет файлы и программы на вашем ПК к тому времени, когда все работало нормально. Произведите следующие шаги:
- Нажмите «пуск».
- В поисковой строке введите «Восстановление системы» и нажмите «ок».
- В окне результатов выберите «Восстановление».
- По инструкциям уже «мастера настроек» завершите работу.
- Запустите проверку системных файлов Windows («sfc /scannow»).
Весьма удобный инструмент, позволяющий просканировать и исправить поврежденные файлы (включая те, что имеют отношение к ошибка 193).
- Выберите «пуск».
- Введите «cmd».
- Запустите от имени администратора.
- Наберите «sfc /scannow» и Enter.
- Проверка начнет сканирование на наличие проблем.
- Завершите процедуру по инструкциям на экране.