Recent content by GrimmyTheReaper

I guess I jumped the gun on fixing it myself. Only other work around i can think of is maybe changing the reference to a external dll file then setting it's properties to embedded resource. I'm not sure if that will work however. Unfortunately I can't test anymore

Ok so I went on a roadabout method and reinstalled the .netframework. I used the link below and it has resolved the issue. I did a manual reinstall of the current release of bnsbuddy with the bnsbuddy updater and it works without issue...

No luck. It works when i put the dll back but does not without it. Sorry for the late reply been a bit busy. And about to go for the night. Side note I've tried reinstalling .net framework and i've also run the "repair tool" provided by microsoft...

System.IO.Compression.dll seems to be the culprit. I removed all other besides this dll and it works. As soon as I move this one it stops working.

That ones works. It loads up. I'm on EU as well. My event viewer still shows errors for it though. EDIT: This is the log from BNSbuddy(doesn't look like any errors there): Creating Settings... Updating Settings... Updated Settings Reading Registry... E:\BnS\BnS\ Reg Key Valid! Path Found! Lang...

Possible references not embedded? Seeing as it's only a single .exe it might be that. I can't find a stack trace but after further investigation on the event viewer i found a Client.exe error as well. See below. EDIT: it's a bit late by me so will update further in the morning.

Yes. EDIT: I've run both sfc and DISM just incase. No errors found.

Debug version same this side. No error popup but in event viewer same error. I'm on windows 10. It seems to be on load error. Something is missing? My upgarde went from v 5.9.7.0 to v 5.9.7.2. I am a c# developer if that helps, if you need me to use a complier such as VS community version let me...

That's all there is to the xml file. There doesn't seem to be any additional errors. I've gone through all times i've tried bnsbuddy in the event viewer. The only difference i see is the report GUID.

Same issue.