A fatal error occurred consult the logs for details scptoolkit - Исправление ошибок и поиск оптимальных решений проблем

I have same problem.

Trying to do fresh install of ScpToolkit v1.6.238.16010 on Windows Pro 64bit Insider Preview.. Here is the log I get when I run «ScpToolkit Driver Installer» as Administrator:

<log4j:event logger="ScpDriverInstaller.MainWindow" timestamp="1454696230452" level="INFO" thread="1"><log4j:message>SCP Driver Installer 1.6.238.16010 [Built: 01/10/2016 14:52:11]</log4j:message><log4j:properties><log4j:data name="log4jmachinename" value="WIN-RNRC4IC2SRR" /><log4j:data name="log4japp" value="ScpDriverInstaller.exe" /><log4j:data name="log4net:UserName" value="WIN-RNRC4IC2SRRmclang" /><log4j:data name="log4net:Identity" value="" /><log4j:data name="log4net:HostName" value="WIN-RNRC4IC2SRR" /></log4j:properties><log4j:locationInfo class="ScpDriverInstaller.MainWindow" method="Window_Initialized" file="" line="0" /></log4j:event>
<log4j:event logger="ScpControl.Driver.NativeLibraryWrapper`1" timestamp="1454696230498" level="DEBUG" thread="1"><log4j:message>Preparing to load DIFxAPI</log4j:message><log4j:properties><log4j:data name="log4jmachinename" value="WIN-RNRC4IC2SRR" /><log4j:data name="log4japp" value="ScpDriverInstaller.exe" /><log4j:data name="log4net:UserName" value="WIN-RNRC4IC2SRRmclang" /><log4j:data name="log4net:Identity" value="" /><log4j:data name="log4net:HostName" value="WIN-RNRC4IC2SRR" /></log4j:properties><log4j:locationInfo class="ScpControl.Driver.NativeLibraryWrapper`1" method="LoadNativeLibrary" file="" line="0" /></log4j:event>
<log4j:event logger="ScpControl.Driver.NativeLibraryWrapper`1" timestamp="1454696230498" level="DEBUG" thread="1"><log4j:message>Called from 64-Bit process</log4j:message><log4j:properties><log4j:data name="log4jmachinename" value="WIN-RNRC4IC2SRR" /><log4j:data name="log4japp" value="ScpDriverInstaller.exe" /><log4j:data name="log4net:UserName" value="WIN-RNRC4IC2SRRmclang" /><log4j:data name="log4net:Identity" value="" /><log4j:data name="log4net:HostName" value="WIN-RNRC4IC2SRR" /></log4j:properties><log4j:locationInfo class="ScpControl.Driver.NativeLibraryWrapper`1" method="LoadNativeLibrary" file="" line="0" /></log4j:event>
<log4j:event logger="ScpControl.Driver.NativeLibraryWrapper`1" timestamp="1454696230498" level="DEBUG" thread="1"><log4j:message>DIFxAPI path: C:Program FilesNefarius Software SolutionsScpToolkitDIFxApiamd64DIFxAPI.dll</log4j:message><log4j:properties><log4j:data name="log4jmachinename" value="WIN-RNRC4IC2SRR" /><log4j:data name="log4japp" value="ScpDriverInstaller.exe" /><log4j:data name="log4net:UserName" value="WIN-RNRC4IC2SRRmclang" /><log4j:data name="log4net:Identity" value="" /><log4j:data name="log4net:HostName" value="WIN-RNRC4IC2SRR" /></log4j:properties><log4j:locationInfo class="ScpControl.Driver.NativeLibraryWrapper`1" method="LoadNativeLibrary" file="" line="0" /></log4j:event>
<log4j:event logger="ScpControl.Driver.NativeLibraryWrapper`1" timestamp="1454696230498" level="DEBUG" thread="1"><log4j:message>Loaded library: C:Program FilesNefarius Software SolutionsScpToolkitDIFxApiamd64DIFxAPI.dll</log4j:message><log4j:properties><log4j:data name="log4jmachinename" value="WIN-RNRC4IC2SRR" /><log4j:data name="log4japp" value="ScpDriverInstaller.exe" /><log4j:data name="log4net:UserName" value="WIN-RNRC4IC2SRRmclang" /><log4j:data name="log4net:Identity" value="" /><log4j:data name="log4net:HostName" value="WIN-RNRC4IC2SRR" /></log4j:properties><log4j:locationInfo class="ScpControl.Driver.NativeLibraryWrapper`1" method="LoadNativeLibrary" file="" line="0" /></log4j:event>
<log4j:event logger="ScpDriverInstaller.MainWindow" timestamp="1454696230498" level="INFO" thread="1"><log4j:message>Microsoft Windows 10 Professional (10.0.10586.0 AMD64) detected</log4j:message><log4j:properties><log4j:data name="log4jmachinename" value="WIN-RNRC4IC2SRR" /><log4j:data name="log4japp" value="ScpDriverInstaller.exe" /><log4j:data name="log4net:UserName" value="WIN-RNRC4IC2SRRmclang" /><log4j:data name="log4net:Identity" value="" /><log4j:data name="log4net:HostName" value="WIN-RNRC4IC2SRR" /></log4j:properties><log4j:locationInfo class="ScpDriverInstaller.MainWindow" method="Window_Initialized" file="" line="0" /></log4j:event>
<log4j:event logger="ScpControl.Driver.NativeLibraryWrapper`1" timestamp="1454696230514" level="DEBUG" thread="1"><log4j:message>Preparing to load libwdi</log4j:message><log4j:properties><log4j:data name="log4jmachinename" value="WIN-RNRC4IC2SRR" /><log4j:data name="log4japp" value="ScpDriverInstaller.exe" /><log4j:data name="log4net:UserName" value="WIN-RNRC4IC2SRRmclang" /><log4j:data name="log4net:Identity" value="" /><log4j:data name="log4net:HostName" value="WIN-RNRC4IC2SRR" /></log4j:properties><log4j:locationInfo class="ScpControl.Driver.NativeLibraryWrapper`1" method="LoadNativeLibrary" file="" line="0" /></log4j:event>
<log4j:event logger="ScpControl.Driver.NativeLibraryWrapper`1" timestamp="1454696230514" level="DEBUG" thread="1"><log4j:message>Called from 64-Bit process</log4j:message><log4j:properties><log4j:data name="log4jmachinename" value="WIN-RNRC4IC2SRR" /><log4j:data name="log4japp" value="ScpDriverInstaller.exe" /><log4j:data name="log4net:UserName" value="WIN-RNRC4IC2SRRmclang" /><log4j:data name="log4net:Identity" value="" /><log4j:data name="log4net:HostName" value="WIN-RNRC4IC2SRR" /></log4j:properties><log4j:locationInfo class="ScpControl.Driver.NativeLibraryWrapper`1" method="LoadNativeLibrary" file="" line="0" /></log4j:event>
<log4j:event logger="ScpControl.Driver.NativeLibraryWrapper`1" timestamp="1454696230514" level="DEBUG" thread="1"><log4j:message>libwdi path: C:Program FilesNefarius Software SolutionsScpToolkitlibwdiamd64libwdi.dll</log4j:message><log4j:properties><log4j:data name="log4jmachinename" value="WIN-RNRC4IC2SRR" /><log4j:data name="log4japp" value="ScpDriverInstaller.exe" /><log4j:data name="log4net:UserName" value="WIN-RNRC4IC2SRRmclang" /><log4j:data name="log4net:Identity" value="" /><log4j:data name="log4net:HostName" value="WIN-RNRC4IC2SRR" /></log4j:properties><log4j:locationInfo class="ScpControl.Driver.NativeLibraryWrapper`1" method="LoadNativeLibrary" file="" line="0" /></log4j:event>
<log4j:event logger="ScpControl.Driver.NativeLibraryWrapper`1" timestamp="1454696230514" level="FATAL" thread="1"><log4j:message>Couldn't load library C:Program FilesNefarius Software SolutionsScpToolkitlibwdiamd64libwdi.dll: System.ComponentModel.Win32Exception (0x80004005): The specified module could not be found</log4j:message><log4j:properties><log4j:data name="log4jmachinename" value="WIN-RNRC4IC2SRR" /><log4j:data name="log4japp" value="ScpDriverInstaller.exe" /><log4j:data name="log4net:UserName" value="WIN-RNRC4IC2SRRmclang" /><log4j:data name="log4net:Identity" value="" /><log4j:data name="log4net:HostName" value="WIN-RNRC4IC2SRR" /></log4j:properties><log4j:locationInfo class="ScpControl.Driver.NativeLibraryWrapper`1" method="LoadNativeLibrary" file="" line="0" /></log4j:event>
<log4j:event logger="ScpDriverInstaller.App" timestamp="1454696230514" level="FATAL" thread="1"><log4j:message><![CDATA[An unexpected error occured on application startup: System.Windows.Markup.XamlParseException: Initialization of 'ScpDriverInstaller.MainWindow' threw an exception. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.DllNotFoundException: Unable to load DLL 'libwdi.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
   at ScpControl.Driver.WdiWrapper.wdi_set_log_level(WdiLogLevel level)
   --- End of inner exception stack trace ---
   at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
   at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
   at System.Activator.CreateInstance(Type type, Boolean nonPublic)
   at ScpControl.Driver.NativeLibraryWrapper`1.CreateInstanceOfT()
   at System.Lazy`1.CreateValue()
   at System.Lazy`1.LazyInitValue()
   at ScpDriverInstaller.MainWindow.Window_Initialized(Object sender, EventArgs e)
   at System.Windows.FrameworkElement.RaiseInitialized(EventPrivateKey key, EventArgs e)
   at System.Windows.FrameworkElement.TryFireInitialized()
   at MS.Internal.Xaml.Runtime.ClrObjectRuntime.InitializationGuard(XamlType xamlType, Object obj, Boolean begin)
   --- End of inner exception stack trace ---
   at System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri)
   at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
   at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
   at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
   at System.Windows.Application.LoadBamlStreamWithSyncInfo(Stream stream, ParserContext pc)
   at System.Windows.Application.DoStartup()
   at System.Windows.Application.<.ctor>b__1_0(Object unused)
   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)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   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)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
   at System.Windows.Application.RunDispatcher(Object ignore)
   at System.Windows.Application.RunInternal(Window window)
   at ScpDriverInstaller.App.Main()]]></log4j:message><log4j:properties><log4j:data name="log4jmachinename" value="WIN-RNRC4IC2SRR" /><log4j:data name="log4japp" value="ScpDriverInstaller.exe" /><log4j:data name="log4net:UserName" value="WIN-RNRC4IC2SRRmclang" /><log4j:data name="log4net:Identity" value="" /><log4j:data name="log4net:HostName" value="WIN-RNRC4IC2SRR" /></log4j:properties><log4j:locationInfo class="ScpDriverInstaller.App" method="&lt;OnStartup&gt;b__0" file="" line="0" /></log4j:event>

Источник

joshg, #5 seems to be related to MTU configuration option. It was already implemented in L2CAP_Configuration_Request, but not L2CAP_Configuration_Response…

Here is sample response with this option.

=== HCI header ===
02 2a 20 12 00 0e 00 01 00 — HCI header, as above, please see the L2CAP CONNECTION REQUEST packet structure

=== Actual L2CAP command ===
05 L2CAP_CMD_CONFIG_RESPONSE
4c Packet identifier
0a 00 Command payload length
40 00 SCID (Source Channel Identifier, in other words, local endpoint ID)
00 00 Flag 0
00 00 Result 0 (success)
01 Config Opt: type = MTU (Maximum Transmission Unit) — Hint
02 Config Opt: length
3c 00 MTU

joshg
PANHAI update from my side: I got it working wireless and with bluetooth. Smile

I apologize upfront as this is going to get a little technical …. but hopefully not too much!

I set up Wireshark with USBPCap in Windows and ran a capture of the bluetooth traffic by having it capture traffic on the USB bluetooth adapter itself, while attempting to connect the controller through bluetooth.

Then also used Wireshark with libpcap in Linux and did the same thing — captured traffic on the USB interface for the bluetooth adapter.

Using this I was able to determine exactly where they are different. Because in Linux it had a lot of built in parsing, plus the libpcap is different than usbpcap used for windows, the output was a little different. So I had to comb through quite a bit and spent about 3 hours analyzing the flow and the individual bytes to finally find where exactly they are different.

So in general different in these few places:

1) When L2CAP_Connection_Request is received, Linux sixad daemon only sends a single L2CAP_Connection_Response with «success» whereas in Windows ScpToolkit is sending 2 individual L2CAP_Connection_Response — first a «pending» followed by a «success».
2) ScpToolkit L2CAP_Command is defaulting 2nd byte (buffer[1]) of the sent buffer to 0x20 if it is 0x00 … in Linux sixad it doesn’t do this, it always is sending 0x00 .. this is for all sending L2CAP commands
3) ScpToolkit L2CAP_Configuration_Request has hard-coded byte of 0x96 and 0x00 for bytes 11 and 12 (buffer[10] and buffer[11]) but I noticed in Linux sixad that it seemed to match DCID (e.g. for mine it was sending 0x40, 0x00) so I changed this to dcid[0] and dcid[1] so it would put the dest channel in these bytes instead of this hard-coded value 0x96, 0x00
4) ScpToolkit L2CAP_Configuration_Response in the 3rd byte (buffer[2]) I noticed in linux for me it was sending 0x0a here but ScpToolkit has this hard-coded at 0x06. For now I changed it to hard-coded 0x0a. From what I have poked around, this value could actually be coming from the controller itself when original HCI_Connection_Request or HCI_Accept_Connection_Request event occurs (on mine I am seeing this byte 0x0a coming across as the next byte after the command/event identifier)
5) Also in same method L2CAP_Configuration_Response, in linux sixad they have 4 extra bytes on the end of this buffer that do not exist in ScpToolkit. They are: 0x01, 0x02, 0xa0, 0x02. The origin of these 4 bytes could possibly be similar to last 4 bytes L2CAP_Configuration_Request and maybe especially this byte 0xa0 could be sent from the controller somewhere in the stream but I haven’t found it as of yet.

Anyway with making those 5 changes to both BthDongle.Tasks.cs and BthDongle.L2cap.cs my PANHAI controllers are working perfectly over bluetooth.

I will try to roll back and maybe make each change one-at-a-time to see if there is one specifically that was the real key or not and post an update shortly Smile

Edit: Ok after trying everything off and on I actually found that only ONE of the above changes is needed and it gets the PANHAI working fine.

It is #5 above — changing L2CAP_Configuration_Response from host to have 14 length payload instead of 10 with 0x01, 0x02, 0xa0, 0x02. Not sure if each of these values can be hard-coded or if they need to depend on data sent back from the controller, but this should be the only change needed to get PANHAI controllers to connect.

I confirmed by taking a fresh copy of source and only modified BthDongle.L2cap.cs:L2CAP_Configuration_Response and it is working with only this change.

Sponsored links

Posts: 28
Threads: 0
Joined: Apr 2016

Reputation:
1

(04-19-2016, 05:48 AM)radixon3 Wrote: So I’ve downloaded scp well, everything, its installed fine but my problem lies with my controller not being recognized by windows, i’ve plugged it into multiple usb ports and a few of them say installing new device drivers or something along those lines, i hear a few beeps and then no lights flash up on my controller, like it doesnt even exist. can anyone help me with this, or did i post in the wrong thread?

Edit- The controller is showing up in devices and printers just fine. Still no battery charging lights and still not detected by scp dualshock 3 setup

Hi radixon3, it almost sounds like there is already a different driver installed for your controllers or the installed driver is disabled or not working right. Have you previously used MotioninJoy or a prior version of Scp?

Which version of ScpToolkit are you using? Latest stable release 1.6.238.16010 or beta? The reason I ask is because the driver installer interface is completely different in the beta vs the stable release from January.

If you are using the stable release 1.6.238.16010 then here’s what I would do.

First unplug all of the controllers so that nothing is connected to your PC.
Run the ScpDriverInstaller.exe and click Uninstall
Run ScpCleanWipe.exe and click the button to wipe away any old drivers.
Next I would also go to Control Panel > Device Manager, then click on View > Show hidden devices. Then open up each of the following and delete any grayed-out entries for game controllers
— Human Interface Devices (they will probably be called something like HID-compliant game controller)
— libusbK devices (look for PS3 GamePad or PS Gamepad or anything similar)
— Universal Serial Bus devices (look for PS3 GamePad or PS Gamepad or anything similar)
— Xbox 360 Peripherals (delete any Xbox 360 controller entries)
After all of this I would then plug the controllers back in to USB and see if they act like they are installing new drivers. Hopefully they should!
After their «driver installation» is complete I would then run the ScpDriverInstaller.exe and install drivers for them (keeping controllers plugged in from step #5 the whole time)

If you are using the latest beta then I am not sure exactly as it looks like ScpDriverInstaller.exe doesn’t give any option to remove or uninstall the drivers. I would probably do each of the following steps above after except excluding ScpDriverInstaller.exe just because I don’t think it is possible? (or I don’t know where it has been moved in the beta, if it is still possible… Smile )

Hope this helps and let us know if this fixes it for you!

Posts: 28
Threads: 0
Joined: Apr 2016

Reputation:
1

(04-19-2016, 04:00 PM)hman77 Wrote: joshg, #5 seems to be related to MTU configuration option. It was already implemented in L2CAP_Configuration_Request, but not L2CAP_Configuration_Response…

Here is sample response with this option.

=== HCI header ===
02 2a 20 12 00 0e 00 01 00 — HCI header, as above, please see the L2CAP CONNECTION REQUEST packet structure

=== Actual L2CAP command ===
05 L2CAP_CMD_CONFIG_RESPONSE
4c Packet identifier
0a 00 Command payload length
40 00 SCID (Source Channel Identifier, in other words, local endpoint ID)
00 00 Flag 0
00 00 Result 0 (success)
01 Config Opt: type = MTU (Maximum Transmission Unit) — Hint
02 Config Opt: length
3c 00 MTU

Thanks hman77 I believe you are right. I suspected this based on what I was seeing in the code but didn’t really dig around in the spec or anywhere else to verify Smile

Also one of my earlier comments regarding MTU and wondering if it is being incorrectly reported using ScpToolkit — well I think now it is being reported correctly because it also comes up in linux as MTU = 672 even detected using the L2CAP standards-based parsing with Wireshark and libpcap.

My ScpControll.dll I posted earlier does not modify to pass the mtu or make the payload length dynamic as was already done in L2CAP_Configuration_Request .. it is more of a brute force. But for a permanent fix (nefarius? Smile ) then I would assume this might need to be done and tested with other controllers (especially genuine ones). I only have these 2 GAME-O pads (PANHAI) so it doesn’t really matter for my use to have this forced in the code because it is working for my controllers Smile

But per your post, it looks like it should be 0x01 (MTU hint), 0x02 (length), then the MTU read from controller. For mine it is 672 (0xa0, 0x02) which is why it is working with 0xa0, 0x02 for me … sounds like the correct fix then, in that case!

Also hman77 just as a friendly and hopefully helpful suggestion, it is a little difficult to read your responses because you have quotes mixed with your text and not using the BBcode for [quote] ing someone .. it almost all looks like your own text until I realize that some of it are things that I wrote Smile

Thanks again and good find!

Posts: 10
Threads: 1
Joined: Jul 2009

Reputation:
0

Hey I was using an older version successfully for over a year, but I decided to update to the latest version. Now everytime I reboot the computer it requires me to reinstall the drivers everytime. If I try run any of the programs (e.g SCPToolkit Profile Manager) I get an error saying:

Oh Shi…
A Fatal error has occurred. Consult the logs for details.

I tried looking at the logs but wasn’t able to open them, but can anyone help me solve this? Reinstalling every time is a bit of a hassle.

Posts: 1
Threads: 0
Joined: Apr 2016

Reputation:
0

04-21-2016, 03:45 AM

SCP has been working great for my Playstation 3 NAV controller — no issues there. I have an XBOX 360 controller now so I can play Dark Souls 3 in Steam. When I connect the XBOX 360 controller it does not work in game. Shows as responsive in Game Controllers and calibration. I do note that it identifies itself as second controller via the LED indicator on the controller. Is this due to the SCP reserving first controller for the PS3 NAV controller when not connected?

If this is the case, is there a way to correct it so I can easily switch between both controllers as required? Any help would be greatly appreciated.

Posts: 1
Threads: 0
Joined: Apr 2016

Reputation:
0

04-22-2016, 01:47 AM
(This post was last modified: 04-22-2016, 01:54 AM by Charged.)

Unfortunately had to uninstall as I’m getting massive NETWORK lag spikes in ANY game while the controller is paired with the PC (wirelessly).

Eg, when I’m playing Rocket League with the controller active, everything is rubberbanding while playing online and I can see the ‘connection error’ icon flashing — turn the controller off, problem goes away.

I can see a lot of work has gone into this software and I’d really like to get it working properly Smile

Please help.

[Windows 10 64]

Posts: 1
Threads: 0
Joined: Apr 2016

Reputation:
0

hi guys

so i just bought this fake ps3 controller and decide to try using XInput Wrapper by Scarlet and when i run Driver Installer it just says

Quote:SCP Driver Installer 1.2.0.160 [4/22/2016 7:32:36 AM]

Detected — Microsoft Windows 7 Ultimate Service Pack 1 (6.1.7601.65536 x86)
Could not find a valid configuration.

so i decided to try ScpToolkit and when i run Driver Installer it show this

http://prnt.sc/av9447

i’m using Windows 7 64 bit
i have checked all the software requirement

Microsoft .NET Framework 4.5
Microsoft Visual C++ 2010 Redistributable Package
Microsoft Visual C++ 2013 Runtime
DirectX Runtime
Xbox 360 Controller driver

i’m only using USB cable to connect the controller
i’ve run the Clean Wipe Utility

idk what else to do..

Posts: 1
Threads: 0
Joined: Apr 2016

Reputation:
0

(04-18-2016, 10:10 PM)joshg Wrote: Link back to https://github.com/nefarius/ScpToolkit/issues/241

And screenshot of both PANHAI pads connected via bluetooth using this code modification

Also I have attached a modified ScpControll.dll zipped in this post if anyone has a PANHAI fake DS3 controller and has been desperately wanting it to work wirelessly for them while waiting on a permanent fix. This was built against ScpToolkit-1.7.277.16103-BETA so you would probably need to use that same version with this file.

My PANHAI controler and a genuine SONY are working perfectly wirelessly (sadly, SONY controller is «broken).

Thanks to Nefarius for his Toolkit and for your modified SCpcontrol.dll .

Posts: 4
Threads: 0
Joined: Feb 2014

Reputation:
0

(04-19-2016, 04:08 PM)joshg Wrote: Hi radixon3, it almost sounds like there is already a different driver installed for your controllers or the installed driver is disabled or not working right. Have you previously used MotioninJoy or a prior version of Scp?

Which version of ScpToolkit are you using? Latest stable release 1.6.238.16010 or beta? The reason I ask is because the driver installer interface is completely different in the beta vs the stable release from January.

If you are using the stable release 1.6.238.16010 then here’s what I would do.

First unplug all of the controllers so that nothing is connected to your PC.

Run the ScpDriverInstaller.exe and click Uninstall

Run ScpCleanWipe.exe and click the button to wipe away any old drivers.

Next I would also go to Control Panel > Device Manager, then click on View > Show hidden devices. Then open up each of the following and delete any grayed-out entries for game controllers
— Human Interface Devices (they will probably be called something like HID-compliant game controller)
— libusbK devices (look for PS3 GamePad or PS Gamepad or anything similar)
— Universal Serial Bus devices (look for PS3 GamePad or PS Gamepad or anything similar)
— Xbox 360 Peripherals (delete any Xbox 360 controller entries)

After all of this I would then plug the controllers back in to USB and see if they act like they are installing new drivers. Hopefully they should!

After their «driver installation» is complete I would then run the ScpDriverInstaller.exe and install drivers for them (keeping controllers plugged in from step #5 the whole time)

If you are using the latest beta then I am not sure exactly as it looks like ScpDriverInstaller.exe doesn’t give any option to remove or uninstall the drivers. I would probably do each of the following steps above after except excluding ScpDriverInstaller.exe just because I don’t think it is possible? (or I don’t know where it has been moved in the beta, if it is still possible… )

Hope this helps and let us know if this fixes it for you!

So i followed all these steps and when I run ScpDriverInstaller and install the drivers, I get a bunch of windows that pop up and then my mouse becomes inoperational and the only way to get it working again is to do a system restore. There’s also a big long error window that pops up with many references to something called dbreeze somethingorother.

Posts: 28
Threads: 0
Joined: Apr 2016

Reputation:
1

(04-23-2016, 11:45 AM)Velz Wrote: So i followed all these steps and when I run ScpDriverInstaller and install the drivers, I get a bunch of windows that pop up and then my mouse becomes inoperational and the only way to get it working again is to do a system restore. There’s also a big long error window that pops up with many references to something called dbreeze somethingorother.

Velz is your mouse wireless with Bluetooth? If so then you may not be able to use it with ScpToolkit.. I know that Nefarius was looking into a way to avoid having the driver for the bluetooth adapter completely taken over so that you could still use other bluetooth devices but I am not sure what the status on this is or if it is even possible.

Источник

Gorefist

16.09.2020

Через стим все работает, остальные проги не нужны. Раньше тоже их использовался, отказался просто в пользу стима.

Для не стим игр, просто запускаешь стим в фоне, все будет работать.

Ответить

Развернуть ветку

Oleg Beloshevich

16.09.2020

Вот да. одно время пользовался дс4вин, и в системе оно хорошо работает, но были какие то проблемы, из-за чего пришлось отказаться. Поддержка стима отличная. Полностью устраивает

Ответить

Развернуть ветку

Французский теркин30см

16.09.2020

А я и не понял как стим заставить увидеть пад, он висел в сопряженных в устройствах, в бигпикчер чот там включал и все. Пришлось после тестов купить ревасд, там до сих пор как часы, дрова их четкие.

Ответить

Развернуть ветку

Аккаунт удален

16.09.2020

Комментарий недоступен

Ответить

Развернуть ветку

SonD.VaNintedno

16.09.2020

запускай все игры, даже пиратки, даже из сторонних лаучнеров через стим, просто добавь exe шник в библиотеку, или лаучнер например origin, через стим запусти ориджин и потом уже игру.
запускай всё через big picture и на всякий случай с английской раскладкой.
проверенно, даже от нинтедно геймпад так работает.

Ответить

Развернуть ветку

lamurchik

16.09.2020

запускай всё через big picture и на всякий случай с английской раскладкой.

Глупость какая.

Ответить

Развернуть ветку

SonD.VaNintedno

16.09.2020

у меня эмулятор демон соулса нормально начинал работать с геймпадом от нинтедно procon только в таких условиях.

Ответить

Развернуть ветку

Аккаунт удален

16.09.2020

Комментарий недоступен

Ответить

Развернуть ветку

Аккаунт удален

16.09.2020

Комментарий недоступен

Ответить

Развернуть ветку

Французский теркин30см

16.09.2020

А вот у меня от этих дров соски дрожали при тесте и в контрол (первое, что стояло на компе) джесси сама по себе ходила и камера шароебилась. При том, что на старых дровах и старой дс4виндовс этой ситуации не было. Странно, не так ли?

Ответить

Развернуть ветку

Людской звук

16.09.2020

соски дрожали

Ответить

Развернуть ветку

Французский теркин30см

16.09.2020

Ггг, кароч не стояли неподвижно в нулевых положениях )))

Ответить

Развернуть ветку

Свободный Мика

16.09.2020

Геймпад точно оригинальный? У меня подобное только с китайцами было.

Ответить

Развернуть ветку

GabeN Stimovitch

16.09.2020

Автор

Да оригинал.Вроде получилось соединить.Только через старую версию проги)

Ответить

Развернуть ветку

Читать все 18 комментариев

Источник

Scp driver installer fatal error

joshg, #5 seems to be related to MTU configuration option. It was already implemented in L2CAP_Configuration_Request, but not L2CAP_Configuration_Response.

Here is sample response with this option.

=== HCI header ===
02 2a 20 12 00 0e 00 01 00 — HCI header, as above, please see the L2CAP CONNECTION REQUEST packet structure

joshg
PANHAI update from my side: I got it working wireless and with bluetooth.

I apologize upfront as this is going to get a little technical . but hopefully not too much!

Then also used Wireshark with libpcap in Linux and did the same thing — captured traffic on the USB interface for the bluetooth adapter.

So in general different in these few places:

1) When L2CAP_Connection_Request is received, Linux sixad daemon only sends a single L2CAP_Connection_Response with «success» whereas in Windows ScpToolkit is sending 2 individual L2CAP_Connection_Response — first a «pending» followed by a «success».
2) ScpToolkit L2CAP_Command is defaulting 2nd byte (buffer[1]) of the sent buffer to 0x20 if it is 0x00 . in Linux sixad it doesn’t do this, it always is sending 0x00 .. this is for all sending L2CAP commands
3) ScpToolkit L2CAP_Configuration_Request has hard-coded byte of 0x96 and 0x00 for bytes 11 and 12 (buffer[10] and buffer[11]) but I noticed in Linux sixad that it seemed to match DCID (e.g. for mine it was sending 0x40, 0x00) so I changed this to dcid[0] and dcid[1] so it would put the dest channel in these bytes instead of this hard-coded value 0x96, 0x00
4) ScpToolkit L2CAP_Configuration_Response in the 3rd byte (buffer[2]) I noticed in linux for me it was sending 0x0a here but ScpToolkit has this hard-coded at 0x06. For now I changed it to hard-coded 0x0a. From what I have poked around, this value could actually be coming from the controller itself when original HCI_Connection_Request or HCI_Accept_Connection_Request event occurs (on mine I am seeing this byte 0x0a coming across as the next byte after the command/event identifier)
5) Also in same method L2CAP_Configuration_Response, in linux sixad they have 4 extra bytes on the end of this buffer that do not exist in ScpToolkit. They are: 0x01, 0x02, 0xa0, 0x02. The origin of these 4 bytes could possibly be similar to last 4 bytes L2CAP_Configuration_Request and maybe especially this byte 0xa0 could be sent from the controller somewhere in the stream but I haven’t found it as of yet.

Anyway with making those 5 changes to both BthDongle.Tasks.cs and BthDongle.L2cap.cs my PANHAI controllers are working perfectly over bluetooth.

I will try to roll back and maybe make each change one-at-a-time to see if there is one specifically that was the real key or not and post an update shortly

Edit: Ok after trying everything off and on I actually found that only ONE of the above changes is needed and it gets the PANHAI working fine.

Источник

its 2017, and there’s still this error #981

Comments

jxv16 commented Nov 21, 2017

‘Oh Sh. A fatal error occured. Consult the logs for details.’

how i fix this? T_T

The text was updated successfully, but these errors were encountered:

rkubes commented Nov 26, 2017

Look through the logs and see if there’s anything that stands out as an error.

They are usually located at: C:Program FilesNefarius Software SolutionsScpToolkitLogs

jxv16 commented Nov 27, 2017

» log4j:messageSCP Driver Installer 1.6.238.16010 [Built: 01/10/2016 09:52:11] log4j:properties
1″ timestamp=»1511537227774″ level=»DEBUG» thread=»1″> Preparing to load DIFxAPI 1″ method=»LoadNativeLibrary» file=»» line=»0″/>
1″ timestamp=»1511537227774″ level=»DEBUG» thread=»1″> Called from 64-Bit process 1″ method=»LoadNativeLibrary» file=»» line=»0″/>
1″ timestamp=»1511537227774″ level=»DEBUG» thread=»1″> DIFxAPI path: F:ScpToolKitDIFxApiamd64DIFxAPI.dll 1″ method=»LoadNativeLibrary» file=»» line=»0″/>
1″ timestamp=»1511537228010″ level=»DEBUG» thread=»1″> Loaded library: F:ScpToolKitDIFxApiamd64DIFxAPI.dll 1″ method=»LoadNativeLibrary» file=»» line=»0″/>
log4j:messageMicrosoft Windows 8.1 Professional (6.3.9600.0 AMD64) detected log4j:properties
1″ timestamp=»1511537228016″ level=»DEBUG» thread=»1″> Preparing to load libwdi 1″ method=»LoadNativeLibrary» file=»» line=»0″/>
1″ timestamp=»1511537228041″ level=»DEBUG» thread=»1″> Called from 64-Bit process 1″ method=»LoadNativeLibrary» file=»» line=»0″/>
1″ timestamp=»1511537228043″ level=»DEBUG» thread=»1″> libwdi path: F:ScpToolKitlibwdiamd64libwdi.dll 1″ method=»LoadNativeLibrary» file=»» line=»0″/>
1″ timestamp=»1511537228269″ level=»FATAL» thread=»1″> Couldn’t load library F:ScpToolKitlibwdiamd64libwdi.dll: System.ComponentModel.Win32Exception (0x80004005): %1 no es una aplicación Win32 válida 1″ method=»LoadNativeLibrary» file=»» line=»0″/>
log4j:message System.Reflection.TargetInvocationException: Se produjo una excepción en el destino de la invocación. —> System.DllNotFoundException: No se puede cargar el archivo DLL ‘libwdi.dll’: No se puede encontrar el módulo especificado. (Excepción de HRESULT: 0x8007007E) en ScpControl.Driver.WdiWrapper.wdi_set_log_level(WdiLogLevel level) — Fin del seguimiento de la pila de la excepción interna — en System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck) en System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) en System.Activator.CreateInstance(Type type, Boolean nonPublic) en ScpControl.Driver.NativeLibraryWrapper`1.CreateInstanceOfT() en System.Lazy`1.CreateValue() en System.Lazy`1.LazyInitValue() en ScpDriverInstaller.MainWindow.Window_Initialized(Object sender, EventArgs e) en System.Windows.FrameworkElement.RaiseInitialized(EventPrivateKey key, EventArgs e) en System.Windows.FrameworkElement.TryFireInitialized() en MS.Internal.Xaml.Runtime.ClrObjectRuntime.InitializationGuard(XamlType xamlType, Object obj, Boolean begin) — Fin del seguimiento de la pila de la excepción interna — en System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri) en System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri) en System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri) en System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream) en System.Windows.Application.LoadBamlStreamWithSyncInfo(Stream stream, ParserContext pc) en System.Windows.Application.DoStartup() en System.Windows.Application. b__1_0(Object unused) en System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) en System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) en System.Windows.Threading.DispatcherOperation.InvokeImpl() en System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) en System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) en System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) en MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state) en System.Windows.Threading.DispatcherOperation.Invoke() en System.Windows.Threading.Dispatcher.ProcessQueue() en System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) en MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) en MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) en System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) en System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) en System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs) en MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam) en MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg) en System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame) en System.Windows.Application.RunDispatcher(Object ignore) en System.Windows.Application.RunInternal(Window window) en ScpDriverInstaller.App.Main()]]> log4j:properties b__0″ file=»» line=»0″/> «

i dont understand this T_T

Syst3mSh0ck commented Dec 2, 2017

It shows ScpDriverInstaller.exe crashed due to System.DllNotFoundException which is a dependency issue, possibly due to UAC. Logs show «Couldn’t load library F:ScpToolKitlibwdiamd64libwdi.dll» and looking up libwdi.dll confirms it to be a Windows Driver Installer library for USB devices which ScpDriverInstaller.exe uses to install the usb miniport class drivers for dualshock support. Make sure you right click on ScpDriverInstaller.exe and Run as Administrator otherwise it won’t work properly.

jxv16 commented Dec 2, 2017

i do that, and still not working T_T

Footer

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Impossible to start SCP DSx Service #543

Comments

TSlion commented Dec 15, 2016

I am using your excellent software for a while now and since I have my new PC, there is a problem with it.
I was able to install the driver to my controller and play with it. But yesterday, I took my controller and connect it to the PS3 of my brother. When I came back home, I tried to use it but it shows me some errors.

So I decided to install the driver again to the controller but I hade the «Oh Sh. A fatal error occured. Consult the log for details» message. I HATE THIS MESSAGE ^^

I tried some old versions, cleared my PC of all scp stuff (Revo uninstaller, registry. ) installed the last version with ScpCleanWipe but still the same problem.

Now, I can see after some long hours of searching that the Scp DSx Service never starting.
Tried Automatic (delayed), tried everything I saw on different topics in this site but never found a fix.

I am desesparate man, please help me or I am gonna be crazy !

The text was updated successfully, but these errors were encountered:

TSlion commented Dec 15, 2016

OMG I’ve found it !
The problem came from a stupid thing.

Right click on «ScpToolkit Driver Installer» Properties -> Compatibility
Then check «Execute this program as compatibility for» and then Select «Vista (Service Pack 2)«

That’s it, all works fine !

DanHolli123 commented Dec 17, 2016

maybe close the issue then?

TSlion commented Dec 17, 2016

Oh yeah you’re right. Thanks !

jxv16 commented Nov 21, 2017

Footer

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Fatal — Couldn’t open the device (DS3 after plugged in via USB) #352

Comments

LoneEch commented Jun 28, 2016 •

I’ve been running into a problem with SCP toolkit, whereas every time I plugged in my PS3 controller after installing its drivers (and running the driver installer, then restarting) it would give me an error stating that it «Couldn’t open the device». I’ve used the clean wipe tool, done the full procedure to uninstall SCP’s drivers and services as a reassurance, and I’ve gone through this several times. I had used Motioninjoy in the past, but I have followed the full removal instructions given by the Emulation General Wiki in order to clean it out of my computer fully (as far as I know at least). I’ve also uninstalled the Xbox controller driver and reinstalled it multiple times, too.

Even with all of these steps, after installing the DS3 drivers from SCP, it still gives me the same error, and prevents me from using my PS3 controller. I do not use Bluetooth, but it also states that it cannot reach the Bluetooth host address for my controller. It’s been plaguing me for a long while now and I really just want to play Rocket League. ;_;

Here’s a screencap of the SCP Server log:

along with a screencap of SCP monitor showcasing the port:

I’m not too sure what else I should add into here, but if I need to please tell me.

The text was updated successfully, but these errors were encountered:

Источник

able to install just fine but no triggers works ie the R1 and R2 what I Faso to work

Bixbies

Alright so I was using my DS3 controller all fine and dandy last night. I plug it in today and received the error «Couldn’t connect to server, please check if the service is running!». I fixed that issue by changing to delayed start up process.

SCP recognizes my controller is plugged in and charging but the controller isn’t working with any of my games. The monitor doesn’t have pop up notifications anymore telling me that the controller is unplugged or plugged in. I also reinstalled (forced) the drivers but nothing seems to work.

Help! (please and thanks)

ScpToolkit_Log-Package_Shanyne_1453164080.zip

Hello,
Today i install ScpToolkit for use my PS4 controler for Steam Games and it’s works.
I install Pscx2 1.4 and i use the pscx2 setting for add customized Xinput 1.3 and Lilipad but when i launch Pscx2 it can’t found Lilipad plugin and Pscx2 freeze and crashed.

Edit : if i delete padPokopom it was work

Exactly what I said in the title.
I’m using Windows 10 x64 (Enterprise) and the latest version of ScpToolkit with a Sony DualShock 3 controller via USB.

I’ve also tried disabling rumble and both the sync/async settings in the Manager but it happens the same.

Thanks in advance!

I get this when installing as administrator. Any ideas?

Using a real Dualshock 3 controller and the latest version of Scp, running the latest version of Windows 10

It seems to install correctly but during gameplay in (just as an example) Street Fighter 4, I randomly get a constant up-left input from either the d-pad or left analog. It stops after a while but starts again randomly.

noxamos

After installation, the service plays the startup sound then stops. The logs (attached) show an exception. If I unplug the controller, start the service, it will run until I plug in the controller.

I usually install only the service and the DS3 driver. The DS4 and Bluetooth checkboxes are not selected. The controller is a QuadStick, which uses a USB report similar to the Afterglow controller.
ScpDsxlogs.zip

nedm89

I just get «a fatal error has occurred. Consult the logs for details.»

How about making ScpToolkit detect Windows upgrades (such as installing a new build of Windows 10) and automatically re-install the Scp driver? I am currently on Insider Preview, so upgrades happen often, and every time I have to manually re-install the Scp Bluetooth driver because Windows Setup re-installs the generic driver.

Is it possible for you to detect the driver being replaced by generic, associate such replacement with an increment in the Windows build number, and do a one-shot driver reinstall after such an event?

I can pair my three DS3 controllers just fine, see them in SCP Monitor normally and use them as XInput controllers. I can plug my DS4 into USB, it shows up and works as XInput as well. But when I try to use the DS4 over Bluetooth, I get the «Sony DualShock 4 found» notification but it dosen’t work at all otherwise. Here’s my logs and screenshot from SCP Server. And yes, I’m normally running SCPService, I only ran the SCP Server app for debug purposes once.

ScpToolkit_Log-Package_Nick_1453654623.zip

Note: Issue #180 was very similar to this, though the creator of that issue closed it because he had a bad Bluetooth dongle.

Is there any way to still use the bluetooth adapter also for my keyboard?
Also my fake controller wont connect while the real ds3 works fine, any idea?

Happens me everytime in Dragon’s Dogma PC.

Zhythe

This problem really made me wanna reset my Windows until I found out that it is that folder who is messing with my hard disk space. Hopefully this will be fixed.

@nefarius: Please respond on my previous topic (#127). I need your help. Thanks in advance.

D-Zen

I have a asus K43SJ laptop with bluetooth module, i install driver for buetooth module and ds3 gamepad, it’s working well but when my laptop wake on from sleep mode, bluetooth module not wake on and not connect with ds3 gamepad, i used ScpToolkit 1.6.238.16010. How to fix it?

r4tzt4r

I’m running Windows 10 (x64). So far I tried the latest release and some of the oldest and I still have this issue. Everything seems normal but suddenly the controller´s left analog stick starts like rapidly moving itself. it registers movement even when I’m not touching it and most buttons stop working. This lasts almost a minute and then it works again. Five minutes later the issue comes back.

Any idea what’s causing this? So far ScpToolkit is the only way I’ve been able to make DS3 work on my W10. Thanks in advance!

When using a USB cable, the controls on the D-pad and sticks sometimes register brief up and up-left input before resetting and doing it again. All this without me touching a thing.

When connected through a bluetooth dongle, these issues go away, but are replaced with others. Now the control sticks sometimes stick the input in games, seconds after you have let go. This happens regardless of asynchronus HID reporting toggled on or off (in Assassin’s Creed Syndicate when in tight spaces and trying to move or deal with the camera and sometimes Rocket League).

Now there’s also a fun one where I played Helldivers, and pressed the L-stick in any direction and then clicking L3 made the game register up-input from the D-pad or sometimes the Square button.

And the best part? None of this shows up in the game controller properties. There, the whole emulation process works perfectly. ^^;

war1ox

Источник

Обновлено: 08.02.2023

Специалист по ремонту и обслуживанию компьютерной и печатающей техники.

Перезагружайте компьютер в безопасном режиме и пробуйте удалить данную программу. Scp Toolkit является не только программой, но и драйвером для устройства. Соответственно при установки или использовании данной программы, могли произойти замена или отключение на уровне драйвера, стандартных устройств ввода, т.е. клавиатуры и мыши.

Bluetooth адаптер перестал работать, как адаптер

Ставил прогу ScpToolkit, которая создавала виртуальный геймпад, так же она Bluetooth адаптер настраивала на локальную работу с геймпадом, превращая адаптер в не работающее что-то с названием Bluetooth Host (ScpToolkit). Прогу я удалил, адаптер нужен, но он уже не работает так, как раньше, как его можно попробовать откатить?

Например, полностью удалить его из системы и установить заново. Хотя, если этот «ScpToolkit» чегойнть начудил в Реестре, то — не поможет.

Я удалял адаптер, ребутнул комп, вставлял в разъем, но он снова определялся не как адаптер.

Евгений Покровский Искусственный Интеллект (173022) А как что? Удалять надо вместе с драйверами.

эта тварь сделала привязку к эсб порту и помогло мне только полное удаление из диспетчера устройств, все следы через мастера удаления и установки программ удалить тоже, скачать официал драйвера и установить новые их на блютуз именно, далее подключить в другой порт в который ранее не втыкалось

Scp toolkit как удалить драйвер

After spending hours installing drivers in safe mode and all manner of other methods, I simply cannot get my DualShock 4 controller to connect to my PC using a USB Bluetooth dongle with Scp Toolkit.

The worst part is that my dongle has now become permanently paired with this program. Does anyone know how I can reset my dongle to its factory settings? Rolling back drivers does not work.

Havent used ScP on this build but didnt it come with an uninstaller?

If that doesnt work
Go to device manager, find Bluettooth device, unistall driver then remove device. Reboot PC. Bt should get reinstalleed automatically without SCP tptakiing coontrol of it.

Could also try windows key + s> type in ‘services’ without ‘ > finnd SCP services > disable it.

Fyi I switched tto Ds4windows for this build because I wanted to use BT adapter with other devices. Once you get coontrol of USB adapter back you could try that.

Oh and one final option would be select a system restore point that was created before you started fiddling with SCP

Havent used ScP on this build but didnt it come with an uninstaller?

If that doesnt work
Go to device manager, find Bluettooth device, unistall driver then remove device. Reboot PC. Bt should get reinstalleed automatically without SCP tptakiing coontrol of it.

Could also try windows key + s> type in ‘services’ without ‘ > finnd SCP services > disable it.

Fyi I switched tto Ds4windows for this build because I wanted to use BT adapter with other devices. Once you get coontrol of USB adapter back you could try that.

Oh and one final option would be select a system restore point that was created before you started fiddling with SCP

Как DriverToolkit заразил ваш компьютер

Анализ показывает, что многие потенциально нежелательные программы проникают без согласия пользователей. Киберпреступники изо всех сил стараются скрыть такое программное обеспечение от глаз пользователя и заставить его установить его непреднамеренно. Эта практика широко используется в сторонних репаках, содержащих дополнительные предложения. Когда пользователи пропускают множество шагов во время установки, они часто пропускают разделы «Дополнительно» или «Пользовательские», чтобы завершить установку как можно быстрее. Это, к сожалению, приводит к тому, что ряд нежелательных приложений попадает на системы из-за халатности пользователей. Зная, что большинство людей не могут позволить себе покупать лицензионное ПО, следует быть более внимательными при загрузке таких программ со сторонних ресурсов. В противном случае вы подвергаете себя риску многократного заражения аналогичными угрозами.

Чтобы полностью удалить DriverToolkit из Windows, мы рекомендуем использовать WiperSoft AntiSpyware от WiperSoft. Он обнаруживает и удаляет все файлы, папки, ключи реестра DriverToolkit и несколько миллионов другого рекламного ПО, хайджекеров и панелей инструментов.

Как удалить DriverToolkit

Разработанная Megaify Software, DriverToolkit — нежелательная программа, предлагающая ряд инструментов для оптимизации производительности вашей системы. Этот список включает в себя исправление ошибок драйверов и обновление программного обеспечения. На первый взгляд, такие возможности определенно улучшают работу вашего компьютера, однако этой конкретной программе нельзя доверять, поскольку она подозревается в создании несуществующих проблем. Это просто означает, что DriverToolkit создает ложный список проблем, говоря, что их необходимо решить немедленно. К сожалению, чтобы избавиться от них, людей просят обновить утилиту до полной версии. Мы уверяем, что гораздо безопаснее вложить эти деньги в проверенные утилиты или загрузить свежие драйверы прямо со страницы разработчика того или иного продукта. Наше руководство ниже поможет вам избавиться от DriverToolkit без следов

Удалите DriverToolkit вручную бесплатно

Ниже приведено пошаговое руководство по полному удалению DriverToolkit из вашего компьютера. Все способы работают в 99% случаев и проверялись на последних версиях DriverToolkit на операционных системах с последними обновлениями и версиями браузеров.

Удалите DriverToolkit из Панели управления

Чтобы начать удаление DriverToolkit, вы должны удалить его с помощью Панели управления. Как правило, данное приложение должно удалиться без проблем, однако мы рекомендуем вам использовать CleanMyPC для очистки остаточных файлов после удаления. Вот инструкции для Windows XP, Windows 7, Windows 8 и Windows 10.

Удалите DriverToolkit из Windows XP:

Нажмите на Start кнопку.
Выберите Панель управления.
Нажмите Установка и удаление программ.
Найдите DriverToolkit.
Нажмите Удалить.

Удалите DriverToolkit из Windows 7:

Нажмите Start кнопку.
Затем перейдите в Панель управления.
Нажмите Удаление программы.
Найдите DriverToolkit и нажмите Удалить.

Удалите DriverToolkit из Windows 8:

Наведите указатель мыши на правый нижний угол, чтобы увидеть Меню.
Нажмите Поиск.
После этого нажмите Приложения.
Затем Панель управления.
Нажмите Удаление программы под Программы.
Найдите DriverToolkit, нажмите Удалить.

Удалите DriverToolkit из Windows 10:

Есть 2 способа удалить DriverToolkit из Windows 10

Первый способ

Нажмите на Start кнопку.
В открывшемся меню выберите Параметры.
Нажмите на Система опцию.
Нажмите Приложения и возможности и найдите DriverToolkit в списке.
Нажмите на нее, а затем нажмите на Удалить кнопку рядом с ней.

Второй способ (классический)

Щелкните правой кнопкой мыши на папку Start кнопку.
В открывшемся меню выберите Программы и компоненты.
Найдите DriverToolkit в списке.
Нажмите на нее, а затем нажмите на Удалить кнопку выше.

Что если не удается удалить DriverToolkit

Перезагрузите компьютер.
Во время загрузки нажмите кнопку F8.
Это действие откроет Дополнительные параметры загрузки меню.
Выберите Безопасный режим и дождитесь загрузки Windows.
Войдите в Панель управления > Программы и компоненты и удалите DriverToolkit

Файлы DriverToolkit:

7z.dll
DPInst32.exe
DPInst64.exe
DriverToolkit.exe
extract.exe
language.ini
msvcp100.dll
msvcr100.dll
network.dll
unins000.dat
unins000.exe
zlibwapi.dll

Папки DriverToolkit:

C:Program Files (x86)DriverToolkit
C:ProgramDataMicrosoftWindowsStart MenuProgramsDriverToolkit
C:Users\AppDataLocalDriverToolkit

Ключи реестра DriverToolkit:

Как заблокировать рекламу и всплывающие окна, предлагающие скачать DriverToolkit

Получите лучшую интернет-безопасность для защиты от таких угроз, как DriverToolkit, в будущем

Одна из самых известных и надежных программ безопасности для Windows — SpyHunter 5. Расширенные алгоритмы и большие базы данных помогают SpyHunter обнаруживать и удалять различные типы угроз. Получите полную защиту от программ-вымогателей, рекламного ПО, шпионского ПО, троянов, вирусов и потенциально нежелательных программ (ПНП), таких как DriverToolkit, с помощью SpyHunter 5. Загрузите его здесь:

Альтернативный инструмент для удаления

Чтобы полностью удалить DriverToolkit из Windows, мы рекомендуем использовать SpyHunter 5 от EnigmaSoft Limited. Он обнаруживает и удаляет все файлы, папки, ключи реестра DriverToolkit и несколько миллионов другого рекламного ПО, хайджекеров и панелей инструментов. Пробная версия SpyHunter 5 предлагает сканирование на вирусы и одноразовое удаление БЕСПЛАТНО.

Читайте также:

Для чего нужен вулканический камень в stands awakening

Red dead online выпито тоников стойкости когда вам было жарко или холодно

На что тратить золото в hearthstone

Как продать скрамджет в гта 5 онлайн

Ассасин черный флаг как улучшить корабль

Источник