error calling setupdigetdeviceregistrypropertyw 122 x360ce как исправить

SetupDiGetDeviceRegistryPropertyA function (setupapi.h)

The SetupDiGetDeviceRegistryProperty function retrieves a specified Plug and Play device property.

Syntax

Parameters

A handle to a device information set that contains a device information element that represents the device for which to retrieve a Plug and Play property.

A pointer to an SP_DEVINFO_DATA structure that specifies the device information element in DeviceInfoSet.

One of the following values that specifies the property to be retrieved:

SPDRP_ADDRESS

The function retrieves the device’s address.

SPDRP_BUSNUMBER

The function retrieves the device’s bus number.

SPDRP_BUSTYPEGUID

The function retrieves the GUID for the device’s bus type.

SPDRP_CAPABILITIES

The function retrieves a bitwise OR of the following CM_DEVCAP_Xxx flags in a DWORD. The device capabilities that are represented by these flags correspond to the device capabilities that are represented by the members of the DEVICE_CAPABILITIES structure. The CM_DEVCAP_Xxx constants are defined in Cfgmgr32.h.

В

SPDRP_CHARACTERISTICS

The function retrieves a bitwise OR of a device’s characteristics flags in a DWORD. For a description of these flags, which are defined in Wdm.h and Ntddk.h, see the DeviceCharacteristics parameter of the IoCreateDevice function.

SPDRP_CLASS

The function retrieves a REG_SZ string that contains the device setup class of a device.

SPDRP_CLASSGUID

The function retrieves a REG_SZ string that contains the GUID that represents the device setup class of a device.

SPDRP_COMPATIBLEIDS

The function retrieves a REG_MULTI_SZ string that contains the list of compatible IDs for a device. For information about compatible IDs, see Device Identification Strings.

SPDRP_CONFIGFLAGS

The function retrieves a bitwise OR of a device’s configuration flags in a DWORD value. The configuration flags are represented by the CONFIGFLAG_Xxx bitmasks that are defined in Regstr.h.

SPDRP_DEVICE_POWER_DATA

(Windows XP and later) The function retrieves a CM_POWER_DATA structure that contains the device’s power management information.

SPDRP_DEVICEDESC

The function retrieves a REG_SZ string that contains the description of a device.

SPDRP_DEVTYPE

The function retrieves a DWORD value that represents the device’s type. For more information, see Specifying Device Types.

SPDRP_DRIVER

The function retrieves a string that identifies the device’s software key (sometimes called the driver key). For more information about driver keys, see Registry Trees and Keys for Devices and Drivers.

SPDRP_ENUMERATOR_NAME

The function retrieves a REG_SZ string that contains the name of the device’s enumerator.

SPDRP_EXCLUSIVE

The function retrieves a DWORD value that indicates whether a user can obtain exclusive use of the device. The returned value is one if exclusive use is allowed, or zero otherwise. For more information, see IoCreateDevice.

SPDRP_FRIENDLYNAME

The function retrieves a REG_SZ string that contains the friendly name of a device.

SPDRP_HARDWAREID

The function retrieves a REG_MULTI_SZ string that contains the list of hardware IDs for a device. For information about hardware IDs, see Device Identification Strings.

SPDRP_INSTALL_STATE

(Windows XP and later) The function retrieves a DWORD value that indicates the installation state of a device. The installation state is represented by one of the CM_INSTALL_STATE_Xxx values that are defined in Cfgmgr32.h. The CM_INSTALL_STATE_Xxx values correspond to the DEVICE_INSTALL_STATE enumeration values.

SPDRP_LEGACYBUSTYPE

The function retrieves the device’s legacy bus type as an INTERFACE_TYPE value (defined in Wdm.h and Ntddk.h).

SPDRP_LOCATION_INFORMATION

The function retrieves a REG_SZ string that contains the hardware location of a device.

SPDRP_LOCATION_PATHS

(Windows Server 2003 and later) The function retrieves a REG_MULTI_SZ string that represents the location of the device in the device tree.

SPDRP_LOWERFILTERS

The function retrieves a REG_MULTI_SZ string that contains the names of a device’s lower-filter drivers.

SPDRP_MFG

The function retrieves a REG_SZ string that contains the name of the device manufacturer.

SPDRP_PHYSICAL_DEVICE_OBJECT_NAME

The function retrieves a REG_SZ string that contains the name that is associated with the device’s PDO. For more information, see IoCreateDevice.

SPDRP_REMOVAL_POLICY

(Windows XP and later) The function retrieves the device’s current removal policy as a DWORD that contains one of the CM_REMOVAL_POLICY_Xxx values that are defined in Cfgmgr32.h.

SPDRP_REMOVAL_POLICY_HW_DEFAULT

(Windows XP and later) The function retrieves the device’s hardware-specified default removal policy as a DWORD that contains one of the CM_REMOVAL_POLICY_Xxx values that are defined in Cfgmgr32.h.

SPDRP_REMOVAL_POLICY_OVERRIDE

(Windows XP and later) The function retrieves the device’s override removal policy (if it exists) from the registry, as a DWORD that contains one of the CM_REMOVAL_POLICY_Xxx values that are defined in Cfgmgr32.h.

SPDRP_SECURITY

The function retrieves a SECURITY_DESCRIPTOR structure for a device.

SPDRP_SECURITY_SDS

The function retrieves a REG_SZ string that contains the device’s security descriptor. For information about security descriptor strings, see Security Descriptor Definition Language (Windows). For information about the format of security descriptor strings, see Security Descriptor Definition Language (Windows).

SPDRP_SERVICE

The function retrieves a REG_SZ string that contains the service name for a device.

SPDRP_UI_NUMBER

The function retrieves a DWORD value set to the value of the UINumber member of the device’s DEVICE_CAPABILITIES structure.

SPDRP_UI_NUMBER_DESC_FORMAT

The function retrieves a format string (REG_SZ) used to display the UINumber value.

SPDRP_UPPERFILTERS

The function retrieves a REG_MULTI_SZ string that contains the names of a device’s upper filter drivers.

A pointer to a variable that receives the data type of the property that is being retrieved. This is one of the standard registry data types. This parameter is optional and can be NULL.

A pointer to a buffer that receives the property that is being retrieved. If this parameter is set to NULL, and PropertyBufferSize is also set to zero, the function returns the required size for the buffer in RequiredSize.

The size, in bytes, of the PropertyBuffer buffer.

A pointer to a variable of type DWORD that receives the required size, in bytes, of the PropertyBuffer buffer that is required to hold the data for the requested property. This parameter is optional and can be NULL.

Return value

SetupDiGetDeviceRegistryProperty returns TRUE if the call was successful. Otherwise, it returns FALSE and the logged error can be retrieved by making a call to GetLastError. SetupDiGetDeviceRegistryProperty returns the ERROR_INVALID_DATA error code if the requested property does not exist for a device or if the property data is not valid.

Remarks

The setupapi.h header defines SetupDiGetDeviceRegistryProperty as an alias which automatically selects the ANSI or Unicode version of this function based on the definition of the UNICODE preprocessor constant. Mixing usage of the encoding-neutral alias with code that not encoding-neutral can lead to mismatches that result in compilation or runtime errors. For more information, see Conventions for Function Prototypes.

Источник

Error Calling Setupdigetdeviceregistrypropertyw 122

We have collected for you the most relevant information on Error Calling Setupdigetdeviceregistrypropertyw 122, as well as possible solutions to this problem. Take a look at the links provided and find the solution that works. Other people have encountered Error Calling Setupdigetdeviceregistrypropertyw 122 before you, so use the ready-made solutions.

https://www.ngemu.com/threads/x360ce-error-setupdigetdeviceregistrypropertyw-122.207024/

Hi, i had the same problem i tried everything but searching in the web i found a solution My system have windows 10 Pro Version 1903 and i did installed the latest from this website

https://stackoverflow.com/questions/50937052/error-code-122-using-setupdigetdeviceregistrypropertyw-to-get-the-required-size

Thanks for contributing an answer to Stack Overflow! Please be sure to answer the question.Provide details and share your research! But avoid …. Asking for …

https://github.com/x360ce/x360ce/issues/914

Is there any fix to this error? I cannot find one and have tried different version of x360ce. See the end of this message for details on invoking just-in-time (JIT) debugging instead of …

https://docs.microsoft.com/en-us/windows/win32/api/setupapi/nf-setupapi-setupdigetdeviceregistrypropertyw

SetupDiGetDeviceRegistryProperty returns TRUE if the call was successful. Otherwise, it returns FALSE and the logged error can be retrieved by making a call to GetLastError. SetupDiGetDeviceRegistryProperty returns the ERROR_INVALID_DATA error code if the requested property does not exist for a device or if the property data is not valid.

https://stackoverflow.com/questions/24356289/setupdigetdeviceregistryproperty-fails-with-error-invalid-data

Looking at the returned values from the different methods, everything seems to work, but the last call to SetupDiGetDeviceRegistryProperty fails with ERROR_INVALID_DATA (that is, the method returns false and GetLastWin32Error yields 13).

Error Calling Setupdigetdeviceregistrypropertyw 122 Fixes & Solutions

We are confident that the above descriptions of Error Calling Setupdigetdeviceregistrypropertyw 122 and how to fix it will be useful to you. If you have another solution to Error Calling Setupdigetdeviceregistrypropertyw 122 or some notes on the existing ways to solve it, then please drop us an email.

Источник

Beta Testing: X360CE 4.8.x.x Alpha #818

Comments

EJocys commented Jul 6, 2018

This issue is for reporting bugs found in Beta Testing: X360CE 4.8.x.x Alpha.

This release contains better exception logging. Removed more old GDB/INI/DLL code. Start with Windows and support for Profiles added. Rest of the focus was on cloud database and multiple profiles support. Default build is AnyCPU now (one x360ce.exe for 32-bit and 64-bit OS). Exclusive 32-bit and 64-bit are still available and I can supply them in the future if there will be problems with MSIL (AnyCPU) builds. Other fixes are listed on release page.

Alpha is intended to test Virtual Emulation. Download links and instructions can be found here:
https://github.com/x360ce/x360ce/blob/master/Wiki/BetaTesting.md

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

We are unable to convert the task to an issue at this time. Please try again.

The issue was successfully created but we are unable to update the comment at this time.

KiNGKiMO commented Jul 6, 2018 •

x360ce crashes at startup:

DllNotFoundException: Unable to load DLL ‘vigemclient.dll’: The specified module could not be found. (Exception from HRESULT: 0x8007007E)

Edit:
Downloaded the missing dll from «x360ce.App.Beta/Resources/ViGEmClient/x64» and it started, but I never had to use vigemclient.dll before.

Edit 2:
I’ve now noticed that x360ce creates «ProgramData\X360CE\Temp\ViGEmClient.dll.84A31178» folder with vigemclient.dll, but this is the x86 version, I replaced with the x64 version I downloaded and it worked. so the correct ViGEmClient.dll needs to be extracted depending on OS architecture I suppose.

KiNGKiMO commented Jul 6, 2018

Can we add Start Minimized? or maybe use the same option selected at Start with Windows?

EJocys commented Jul 6, 2018 •

@KiNGKiMO: Thanks for reporting. Fixed VigemClient.dll issue. X360CE.exe process is using it, so it extracts correct one now (Depending on which architecture, 32-bit or 64-bit, x360ce application runs at the moment).

Yes, you can start minimised. There are two options to do that. You can:

a) Start executable with «WindowState»option. Example: x360ce.exe /WindowState=Minimized
b) Create shortcut (for example on the Desktop). Open shortcut properties via right-mouse click and set «Run:» option to Minimised.

You can re-donwload latest update from here: https://github.com/x360ce/x360ce/releases
Edit: Re-uploaded release zips with correct 4.8.0.14 version.

KiNGKiMO commented Jul 6, 2018

@EJocys Thank you.
Updated release works just fine.

EJocys commented Jul 6, 2018

Note: Each file have XML comment inside at the top, which describes its purpose. Some of files will be larger later, because most popular world settings will be stored in them, so that x360ce application can set many controllers correctly automatically without connecting to the Internet.

Squall-Leonhart commented Jul 10, 2018 •

So im not getting the stuck vibration when starting x360ce anymore, but I’m not getting directional constant vibration with the constant setting either.

Swap motors is either both small or both large instead of swapping the 2.

Edit
And now its working after toggling «Enable force feedback»

So it seems FFB is still not initializing properly at a fresh start

Squall-Leonhart commented Jul 10, 2018

Fix force feedback not working when controller re-connected.

This is still not working in 4.8.0.14

EJocys commented Jul 10, 2018

@Squall-Leonhart Maybe, I fixed just part of the problem. I will try to replicate the issue again.

KiNGKiMO commented Jul 13, 2018

@EJocys
`Enabling Virtual Drivers:

[Issues] tab will start blinking it Virtual Drivers are missing.
Press [Issues] tab and hit [Install] button to install Virtual Controller Drivers.`

This is not happening, I’ve tried it uninstalling ViGEM Bus and nothing at [Issues] tab. Please recheck.

Squall-Leonhart commented Oct 14, 2018 •

there are updates to vigembus for a couple of bsod issues that we should take in, and hidguardian has been overhauled.

KiNGKiMO commented Oct 14, 2018

@Squall-Leonhart
This explains the BSOD I get every now and then.

New versions of hidguardian are totally different as i recall. Will need to be re-implemented in x360ce to work correctly.

Squall-Leonhart commented Oct 14, 2018

it might, but it also might not.

KiNGKiMO commented Oct 16, 2018

@EJocys Any new alphas after hidguardian update? I didn’t know there’s a 1.14.3.0 version.

KiNGKiMO commented Dec 12, 2018 •

I tried x360ce today on an old machine (Core 2 Quad Processor Q9650/8GB RAM) Fresh installed Windows 10 ltsc 2019.
I tested Pro Evolution Soccer 2018 and the frame rate drops from 60 to 5x while using x360ce making stuttering effects at the game.

The game works just fine with x360ce closed though.

This is the 1st time I’m facing such issue. Any ideas?

Edit:
Well, I’ve discovered that it has nothing to do with x360ce. It’s the game itself, it works just fine if the Stadium settings were set to «Night». it was random before, so when it’s «Day» the game stutters on older CPUs.

tmarquesbr commented Dec 14, 2018

@KiNGKiMO I saw that once with some games and I got help. I tried to turn off «Enable Force Feedback» and that worked for me. The motor won’t work but.

Also, I found two issues using a pair of controllers here. I don’t know if that can count as a bug (and I didn’t find any solution here), but.

Controllers used for this: Ipega PG-9076 (bluetooth, wired and USB dongle) and a B-MAX (wired)

NullReferenceException: Referência de objeto não definida para uma instância de um objeto.System.NullReferenceException: Referência de objeto não definida para uma instância de um objeto.
at x360ce.Engine.Data.UserDevice.LoadHidDeviceInfo(DeviceInfo DeviceInfo)

The controller works wired and with a USB dongle, which is a workaround for me. I don’t have another bluetooth controller to check for more issues (sorry). Tried to turn off any HiD but not only failed but the controller fails to connect with x360ce.

Источник

Джойстик (контроллер) не определяется в игре — x360 CE

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

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

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

Может, конечно, это как-то связано с тем, что девайс староват (хотя моя версия Logitech ‘а еще есть в продаже и на сайте производителя даже заявлена поддержка Windows 10), но судя по информации с форумов, проблема актуальна повсеместно и носит достаточно частый характер.

Сегодня мы поговорим о возможном решении этой ситуации.
Давайте приступим.

Чаще всего проблема связана с библиотекой xinput1_3.dll и в интернете предлагают самые разные решения, вроде переустановки DirectX, скачивания и регистрации библиотеки насильно и много чего еще. Мы всем этим заниматься не будем, т.к нам необходимо решить вполне конкретную проблему и делать мы это будем вполне определенным инструментом.

Само собой, что в рамках этой статьи мы предполагаем, что драйвера для джойстика (контроллера) у Вас скачены и установлены с сайта производителя или с диска, который шел в комплекте.. Либо установлены системой автоматически.

Скачать программу можно с сайта разработчика. Выберите версию для разрядности своей системы (x32 или x64) и скачайте соответствующий дистрибутив как показано на скриншоте выше (во всяком случае он был актуален на момент написания статьи).

Возможно, что Вы столкнетесь с ошибкой, которая представлена на скриншоте выше (он кликабелен). В нашем случае это нормально и необходимо просто нажать в кнопку » Greate «.

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

Рекомендуется оставить всё как есть и нажать в кнопку » Next «, обычно необходимые настройки будут подгружены автоматически о чем будет свидетельствовать соответствующее окно.

После чего нажать в кнопочку » Finish «. Если Вы увидите ошибку как на скриншоте ниже, то нажмите в кнопку » Продолжить «.

Если Вы всё сделали правильно (или наоборот никаких окон автоматически не появлялось и Вы ничего не поняли), то в первой вкладке у Вас должна определится некая раскладка (все эти Button 1, Button 2 и тп):

А по нажатию на кнопку Game Controller (скриншот выше кликабелен) открываться список игровых устройств, где, собственно должен быть джостик в состоянии ОК (он кстати может называться не так как в реальности, но не это главное).

Далее Вам необходимо либо:

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

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

Завершив все настройки и нажав в » Save » программу необходимо закрыть, после чего все три полученных файла в папку с игрой, а именно:

Возможные вариации файла:

На сим всё, можно запускать и играть.
А мы переходим к послесловию.

Послесловие

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

Как и всегда, если есть какие-то вопросы, мысли, дополнения и всё такое прочее, то добро пожаловать в комментарии к этой записи.

Источник

how to fix usb gamepad not detected x360ce error calling setupdigetdeviceregistryproperty 122

Для просмотра онлайн кликните на видео ⤵

Solved. x360ce error calling setupdigetdeviceregistryproperty 122Подробнее

[FIXED] : x360ce All Errors Fixed. Подробнее

How To Fix x360ce «Failed to load xinput1_3.dll» or «Error 0x80004005» (Latest Guide)Подробнее

How to fix gamepad controller for all games || all errors fix for any game ||Подробнее

Fix Gamepad not Detected or not recognized in xbox 360ce | Play PC Game with ControllerПодробнее

Fix x360ce Error PAD0 Misconfigured device, check GUIDs in 4 MinutesПодробнее

Что делать если не работает Xbox 360 Controller Emulator (x360ce)Подробнее

Generic USB controller to XBox360 Controller | No Copy Pasting | No x360ceПодробнее

Как настроить геймпад через x360ce v4Подробнее

How to fix Gamepad Controller for all pc gamesПодробнее

Fixing [PAD0] Misconfigured device, check GUIDs error from x360ceПодробнее

⚡ Fix x360ce «Failed To Load Xinput1_3.dll /Error 0x80004005» WORK-100% (2020) ⚡Подробнее

X360CE Fix Camera Rotation Analog Step By StepПодробнее

Fix»Unhandled exception had occurred in your application»error for your xbox360ce gamepad emulatorПодробнее

x360ce not detecting controller?Подробнее

(FIXED) HOW TO RESET OR UNINSTALL X360CEПодробнее

Fixing error of Avengers Game not detecting the Gamepad using the x360e (STEP TO STEP GUIDE).Подробнее

Источник