bcrypt.dll

[paulv2k4]

Some more testing produced the following results.

Difference between the two machines.
Laptop is Intel, PC is AMD. (Not sure that matters)
Laptop is Win10 Home, PC is Win10 Pro. (I can upgrade to Pro if I need to but it will be a pain - we all know how awful the Win10 upgrade system is)

PC
no problem no matter what bcrypt.dll I use.

Laptop.

Latest bcrypt.dll from alpha4.
- Will not launch from Frosty Editor

bcrypt.dll from alpha3
- No mods applied - Load FrostyEditor and launch FIFA 18 successfully
- Apply any change - Load FrostyEditor and wont launch the game (just quickly shows fifaconfig and busy symbol)

Hazliv's graphics initfs or RC initfs
- Click Play Game and it quickly blinks then closes

Any other ideas guys? I REALLY don't want to go down the road of building the bcrypt.dll myself. Are there any other bcrypt.dll flying around?

 

[Chuny]

Are there different bcrypt.dll? I thought everyone was sharing the same one and all that changed was the initfs_Win.dll

This year is so confusing for me haha

 

[Sami 1999]

Some more testing produced the following results.

Difference between the two machines.
Laptop is Intel, PC is AMD. (Not sure that matters)
Laptop is Win10 Home, PC is Win10 Pro. (I can upgrade to Pro if I need to but it will be a pain - we all know how awful the Win10 upgrade system is)

PC
no problem no matter what bcrypt.dll I use.

Laptop.

Latest bcrypt.dll from alpha4.
- Will not launch from Frosty Editor

bcrypt.dll from alpha3
- No mods applied - Load FrostyEditor and launch FIFA 18 successfully
- Apply any change - Load FrostyEditor and wont launch the game (just quickly shows fifaconfig and busy symbol)

Hazliv's graphics initfs or RC initfs
- Click Play Game and it quickly blinks then closes

Any other ideas guys? I REALLY don't want to go down the road of building the bcrypt.dll myself. Are there any other bcrypt.dll flying around?

Is your Win 10 Home updated to the latest Fall creator's update?

You may try installing a Windows 10 pro on your laptop using virtual machine if you don't want to upgrade to Pro right away.


Also, Windows 10 as a whole is very confusing. Everything worked before but then FiFA 2005~2010 stopped working when I updated to creators update. I thought I was out of luck. MS support was useless as usual. Then I figured that Enabling Legacy Feature On [Why did they turn it off to begin with] fixed the issue.

Windows defender tried to delete RC's and Fidel's mods thinking its a malware. I had to specifically add the whole Origin Games folder as an exception to avoid these issues.


You should see if its your antivirus that's blocking the bcrypt.dll

Right click on bcrypt.dll and go to properties. Make sure you Unblock the file [This block shit came to existece after the latest windows update].

^If the above suggestions don;t work for you, I really don't know what can be the issue.

 

[Fidel Gameplay]

For me sounds like an hardware incompatibility. In the fact laptop use a bit different driver architecture etc.
Try to completely kill framework software, web cam integrated software, start win only in default services enabled in msconfig.
Disable antivirus. Full rights to the fifa 18 folder. Frisgon solved with alselsdk library (warranty voider dll).
Also is required to close any addon tray related to gpu, Fraps, etc. Try out.
For example to solve the issue finally: every user with issue will share pc specs, so and pc used
at end will check out to analize post with issue and check to solve.
For me the issue is related by an incompatibility with a third party app in Windows. Bye

 

[Sami 1999]

That makes sense.

I've GeForce Experience installed [For taking screenshots] and RTSS installed for fixing Frame pacing issues. Maybe those are interfering the bcrypt.dll

 

[Chuny]

Are there different bcrypt.dll? I thought everyone was sharing the same one and all that changed was the initfs_Win.dll

Anyone?

 

[paulv2k4]

Okay.

I re-formatted my laptop with Win10 Pro 1703 (not fall update) and only installed Origin, FIFA 18 and Frosty Editor (absolutely no bloatware, no antivirus, no windows defender - disabled via group policy).

Still not working!!

So this is fast becoming a hardware, not software, issue.

On this course, it looks like Modding FIFA will only work for select machines :/

 

[Grimbarian]

Does event viewer show any errors?

 

[paulv2k4]

Ok I have decided to give up for now. So I can only mod on my PC (which is REALLY a problem for me as I am rarely home).

I have raised an issue on GitHub for galaxyman to look at.

https://github.com/GalaxyEham/FrostyToolSuite/issues/37

Its not a surprise that the Mod Manager doesn't work either. So there is something substantially wrong with the way this is working. I think it will be hard to debug unless GalaxyMan is willing to let me debug his code on my laptop.

EDIT:

Does event viewer show any errors?

Just read this after posting. Will take a look.

 

[bromireal]

Ok I have decided to give up for now. So I can only mod on my PC (which is REALLY a problem for me as I am rarely home).

I have raised an issue on GitHub for galaxyman to look at.

https://github.com/GalaxyEham/FrostyToolSuite/issues/37

Its not a surprise that the Mod Manager doesn't work either. So there is something substantially wrong with the way this is working. I think it will be hard to debug unless GalaxyMan is willing to let me debug his code on my laptop.

EDIT:



Just read this after posting. Will take a look.

I was having problems with bcrypt too, then I copied bcrypt and the anselsdk dlls to fifa main folder.
And init started to work.
I have 2 partitions on the same system
One with win 8.1 and one with win 10
Initfs is now working fine with both partitions.

Frosty editor is working fine with both partitions.
Frosty Mod Manager is working fine on win 8.1 while on win 10 it loads fine and I also can load the mods but when I click "launch" I get these error message:

Value cannot be null.
Parameter name: value

   at System.Security.Cryptography.AesCryptoServiceProvider.set_Key(Byte[] value)
   at FrostySdk.FileSystem.‫‭‌‭‫‬‏‭‎‪‎‎‫‏‫‍‍‍‫‫‌‬‍‏‏‌‮(Byte[] )
   at FrostySdk.FileSystem.Initialize(Byte[] key)
   at FrostyModManager.MainWindow.<launchButton_Click>d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

 

[paulv2k4]

I threw everything I had at this.

After I reformatted my Win 10 Home to Pro. (which made no difference)

I then decided to take a different approach. I uninstalled & deleted the folders of my FIFA 18 & FIFA 17.

I placed FrostyEditor on my C (Windows) Drive in its own folder named "FrostyEditor". I placed all my modding project work in the same folder within a subfolder. I re-installed FIFA 18 from Origin. I run Frosty as Adminstrator and it worked.

I am thinking that there an issue with Origin, FIFA & Frosty. So I think the full reinstall and clean start to the whole thing fixed it all.