Well, i'm lost :-/ Anyone can help?

Hi,

So, i previously i had the original SCP package, uninstalled as per instructions, installed BthPS3, DsHidMini and DS4Windows and been happy since (i'm using a DS3).

Yesterday, for some resons (?), it started disconnecting by itself (BT). Connected with cable, that didn't help.

Rebooted, and with cable was ok. I didn't mind anymore.

Today i started using it and it disconnected again after a while; this time a reboot didn't help.

I proceeded to uninstall DsHidMini and BthPS3 (following instructions), redo everything from zero but no success.

What happens is:

under device manager i see this:
7910a004-66db-49d9-9c18-e743d1769a39-image.png

In properties it says this:
ca8cacf0-e4f7-4c87-8995-953ac903074e-image.png Wich translated to something like "Impossible to start the device. Configuration informations in system registry are incomplete or damaged (Code 19)"

So i uninstalled everything again, searched the registry for "DS3 Compatible HID Device", deleted all corrisponding keys, reboot, reinstalled everything.

Same situation.

I have another DS3 here and a couple of SixAxis; with all of them the result is the same.

Connecting by cable the DS3 all leds on it stay black; if i press the PS button they start to flash (all together) for a while and that's all.

DSHMC.exe doesn't report any compatible device connected.

Also, strangely, despite being the latest version of it avaiable (2.0.248.0) it reports as there's a new version avaiable (!?)
e13f7416-97b6-4c12-8e8f-04828d310fd6-image.png

Any help to get me out of this loophole would be greatly appreciated.

C.

@dhstsw said in Well, i'm lost 😕 Anyone can help?:

Also, strangely, despite being the latest version of it avaiable (2.0.248.0) it reports as there's a new version avaiable (!?)

Not strange at all, there is a newer version available 😛

92babdae-4c4d-4f36-a386-13c217b3ff6f-image.png

@dhstsw said in Well, i'm lost 😕 Anyone can help?:

In properties it says this:

Wich translated to something like "Impossible to start the device. Configuration informations in system registry are incomplete or damaged (Code 19)"

Did you forget to install the 2nd INF?

@nefarius

Hi.

So, i failed to see version 2.2.282 because the link in the notification:

b5f0f7af-84aa-401e-8b2f-eac095658d6c-image.png

Links directly to https://github.com/ViGEm/DsHidMini/releases/tag/v2.0.248.0 (i guess becase the last one is still beta?)

As for igfilter.inf:

-Removal instructions don't mention to remove it;
-Never the less (after all the removal/reinstall described above) i tried to remove it with Driver Store Explorer but (even forcing it) it doesn't remove.
-I tried anyway to "install it" (hoping o an overwrite) but, while it gave me "install ok" confirmation, contrary to dshidmini.inf, it didn't request administrative permission to install.

So, igfilter is there.

Currently the situation is as follows:

872c140a-7a70-408b-906e-8b2cd4d2cf50-image.png

I'm downloading the 'real' 🙂 latest version and try again everything with that. I'll report back.

Thanks.

C.

So, installed 2.2.282.0.

Same situation:

f8c4c2d4-b51a-4797-bb4c-d50cf7ca8ed6-image.png

Driver Store Explorer reports as follow:

b73085ad-5079-43c9-a9e3-8c92bb3751f9-image.png

And the same in Device manager:
6e20f85d-ed25-4454-8cfe-7f3d49f007e9-image.png 3ef2d05f-8519-4775-841a-dffee220819a-image.png

😞

@dhstsw said in Well, i'm lost 😕 Anyone can help?:

Links directly to https://github.com/ViGEm/DsHidMini/releases/tag/v2.0.248.0 (i guess becase the last one is still beta?)

That is correct, the Beta releases are not linked by "latest" unless they're switched to "official", that is a GitHub feature and works as intended. Now you know 😉

Nonetheless the version should have little to do with this issue since it's not a known bug.

Try this: unplug everything, open regedit and delete this key Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_054C&PID_0268 then plug it in and see if it's fixed. For wireless delete everything under Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\BTHPS3BUS

Cheers

@dhstsw said in Well, i'm lost 😕 Anyone can help?:

-I tried anyway to "install it" (hoping o an overwrite) but, while it gave me "install ok" confirmation, contrary to dshidmini.inf, it didn't request administrative permission to install.

This happens because it was already installed in the same version so it just skips the installation. That is fine.

@nefarius

Hi really needed to have it back, i restored a backup and now it seems to work, but if it happened before i guess it will happen again.
If it does i'll try with your registry instructions and report back.

TY for now 🙂
C.

This post is deleted!
This post is deleted!

@nefarius

So, it happened again.

I went to regedit and deleted the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_054C&PID_0268

riconnecting the DS3, same situation:
ebaf6bdf-143c-4b91-9192-0bf75abcfa52-image.png

Disconnected the DS3, deleted again the key, uninstalled dshidimini, reboot, install it again, connected the DS3, same situation.

I'm clueless.

If it may be of any help, here's the (recreated) key:

506bb016-3a13-42ec-97d0-63e2b96e878b-image.png

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_054C&PID_0268]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_054C&PID_0268\6&16bfd654&0&16]
"DeviceDesc"="@oem107.inf,%ds3devicename%;DS3 Compatible HID Device"
"LocationInformation"="Port_#0016.Hub_#0001"
"Capabilities"=dword:00000004
"Address"=dword:00000010
"ContainerID"="{f2286d79-4a37-11ec-85a7-94b86db63752}"
"HardwareID"=hex(7):55,00,53,00,42,00,5c,00,56,00,49,00,44,00,5f,00,30,00,35,\
  00,34,00,43,00,26,00,50,00,49,00,44,00,5f,00,30,00,32,00,36,00,38,00,26,00,\
  52,00,45,00,56,00,5f,00,30,00,31,00,30,00,30,00,00,00,55,00,53,00,42,00,5c,\
  00,56,00,49,00,44,00,5f,00,30,00,35,00,34,00,43,00,26,00,50,00,49,00,44,00,\
  5f,00,30,00,32,00,36,00,38,00,00,00,00,00
"CompatibleIDs"=hex(7):55,00,53,00,42,00,5c,00,43,00,6c,00,61,00,73,00,73,00,\
  5f,00,30,00,33,00,26,00,53,00,75,00,62,00,43,00,6c,00,61,00,73,00,73,00,5f,\
  00,30,00,30,00,26,00,50,00,72,00,6f,00,74,00,5f,00,30,00,30,00,00,00,55,00,\
  53,00,42,00,5c,00,43,00,6c,00,61,00,73,00,73,00,5f,00,30,00,33,00,26,00,53,\
  00,75,00,62,00,43,00,6c,00,61,00,73,00,73,00,5f,00,30,00,30,00,00,00,55,00,\
  53,00,42,00,5c,00,43,00,6c,00,61,00,73,00,73,00,5f,00,30,00,33,00,00,00,00,\
  00
"ClassGUID"="{2b959c9d-a4ed-4464-809d-0f1118cf055d}"
"Driver"="{2b959c9d-a4ed-4464-809d-0f1118cf055d}\\0004"
"LowerFilters"=hex(7):57,00,55,00,44,00,46,00,52,00,64,00,00,00,6e,00,73,00,73,\
  00,6d,00,6b,00,69,00,67,00,00,00,00,00
"Mfg"="@oem107.inf,%manufacturerstring%;Nefarius Software Solutions e.U."
"Service"="mshidumdf"
"ConfigFlags"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_054C&PID_0268\6&16bfd654&0&16\Device Parameters]
"DeviceResetNotificationEnabled"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_054C&PID_0268\6&16bfd654&0&16\Device Parameters\WUDF]
"DriverList"=hex(7):64,00,73,00,68,00,69,00,64,00,6d,00,69,00,6e,00,69,00,00,\
  00,00,00
"MethodNeitherAction"=dword:00000001
"KernelModeClientPolicy"=dword:00000001
"FileObjectPolicy"=dword:00000001
"FsContextUsePolicy"=dword:00000001
"HostPriority"=dword:00000002
"UmdfDispatcher"="NativeUSB"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_054C&PID_0268\6&16bfd654&0&16\Device Parameters\WUDFDiagnosticInfo]
"HostPid"=hex(b):94,22,00,00,00,00,00,00
"LifetimeID"="732f229e-e242-4959-afb1-47168ceb2ee5"
"RetrievalMode"=dword:00000001
"RwTransferMode"=dword:00000000
"IoctlTransferMode"=dword:00000000

Update: i tried to do a W10 install "in place" (usually this solve a lot of issues), but no happiness 😞

Update 2:
After a lot of unsinstall, reinstall, registry cleaning and so on not it looks like it's working again 🙂

C.