inf files - ClassInstall32 now banned?

I am trying to get some drivers to migrate to win10 (with visual studio (!!!) 2017) stampinf is telling me that I have an

“error 1307: Found legacy AddReg operation defining class installers (Installer32).”

(https://msdn.microsoft.com/en-us/ie/dn932574(v=vs.94)#device_devfund_inf_classinstall32)
"Developers should use one of the existing inbox device setup classes for their device. If it is necessary to define a new device setup class, the new setup class cannot employ a class installer as part of the device installation process. "

So I cant install my own custom setup class? Really?!

Does anyone know a workaround for this? (Farewell Innovation/ Hello “InBox” :slight_smile: )

Any thoughts greatly appreciated,

Jolyon

The goal is to move to an entirely declarative install. Invoking third party code into the install path leads to lesss reliable installs. What is your class installer doing that can?t be done declaratively?

Bent from my phone


From: 30141527200n behalf of
Sent: Wednesday, June 6, 2018 9:02 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] inf files - ClassInstall32 now banned?

I am trying to get some drivers to migrate to win10 (with visual studio (!!!) 2017) stampinf is telling me that I have an

“error 1307: Found legacy AddReg operation defining class installers (Installer32).”

(https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmsdn.microsoft.com%2Fen-us%2Fie%2Fdn932574(v%3Dvs.94)%23device_devfund_inf_classinstall32&data=02|01|Doron.Holan%40microsoft.com|046d1af511eb4864f4d008d5cbc6dec4|72f988bf86f141af91ab2d7cd011db47|1|0|636638977355719309&sdata=Ou6%2FuSH%2Bi4w3Nf5hDDAloxM5iQxDOvNml%2Bh01dUrcKY%3D&reserved=0)
"Developers should use one of the existing inbox device setup classes for their device. If it is necessary to define a new device setup class, the new setup class cannot employ a class installer as part of the device installation process. "

So I cant install my own custom setup class? Really?!

Does anyone know a workaround for this? (Farewell Innovation/ Hello “InBox” :slight_smile: )

Any thoughts greatly appreciated,

Jolyon


NTDEV is sponsored by OSR

Visit the list online at: https:

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at https:

To unsubscribe, visit the List Server section of OSR Online at https:</https:></https:></https:>

You can make your own class if you’d like to, but you can’t have a class installer as part of the class.

-----Original Message-----
From: xxxxx@lists.osr.com On Behalf Of xxxxx@gmail.com
Sent: Wednesday, June 6, 2018 9:01 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] inf files - ClassInstall32 now banned?

I am trying to get some drivers to migrate to win10 (with visual studio (!!!) 2017) stampinf is telling me that I have an

“error 1307: Found legacy AddReg operation defining class installers (Installer32).”

(https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmsdn.microsoft.com%2Fen-us%2Fie%2Fdn932574(v%3Dvs.94)%23device_devfund_inf_classinstall32&amp;data=02|01|zac.lockard%40microsoft.com|749d544d80c44703b7b108d5cbc6e7af|72f988bf86f141af91ab2d7cd011db47|1|0|636638977507197541&amp;sdata=H5thRal2Vh8c%2F6lfWTo5IU49WdSuqy%2FcJxFmVlt%2FB1o%3D&amp;reserved=0)
"Developers should use one of the existing inbox device setup classes for their device. If it is necessary to define a new device setup class, the new setup class cannot employ a class installer as part of the device installation process. "

So I cant install my own custom setup class? Really?!

Does anyone know a workaround for this? (Farewell Innovation/ Hello “InBox” :slight_smile: )

Any thoughts greatly appreciated,

Jolyon


NTDEV is sponsored by OSR

Visit the list online at: https:

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at https:

To unsubscribe, visit the List Server section of OSR Online at https:</https:></https:></https:>

That’s good news… because this has been a MAJOR issue that I’ve been going on about for over a year.

Tell me, please: HOW can you have your own device class? The entire ClassInstall32 section LOOKS like it’s be banned from DCHU INF files? Is that NOT the case?

Peter
OSR
@OSRDrivers

DCHU doesn?t allow for you to create your own class. If you don?t need to conform to DCHU, you can still create the class. Hardware dev center will still allow an inf that creates the class, it will not be applicable across all windows editions.

d

Bent from my phone


From: 30201522300n behalf of
Sent: Wednesday, June 6, 2018 11:14 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] inf files - ClassInstall32 now banned?

That’s good news… because this has been a MAJOR issue that I’ve been going on about for over a year.

Tell me, please: HOW can you have your own device class? The entire ClassInstall32 section LOOKS like it’s be banned from DCHU INF files? Is that NOT the case?

Peter
OSR
@OSRDrivers


NTDEV is sponsored by OSR

Visit the list online at: https:

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at https:

To unsubscribe, visit the List Server section of OSR Online at https:</https:></https:></https:>

Thank you, Mr. Holan.

Sadly, that’s what I thought.

Peter
OSR
@OSRDrivers

To be a bit more precise, ClassInstall32 is not allowed in DCHU drivers, but *is* allowed in DCH drivers. The current requirements only require DCH compliance, although I don’t know if/when U will be required.

-----Original Message-----
From: xxxxx@lists.osr.com On Behalf Of xxxxx@osr.com
Sent: Wednesday, June 6, 2018 12:25 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] inf files - ClassInstall32 now banned?



Thank you, Mr. Holan.

Sadly, that’s what I thought.

Peter
OSR
@OSRDrivers


NTDEV is sponsored by OSR

Visit the list online at: https:

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at https:

To unsubscribe, visit the List Server section of OSR Online at https:</https:></https:></https:>

Thanks for clarification on this - in response to doran’s query about “what offbeat thing are you trying to do that has to be done like this?”… it’s the oldest answer in the book - I am trying to avoid fixing something that works :-)… or perhaps work*ed* (sigh)

thanks again

Jolyon

peter v - i read your thoughts in this thread http://www.osronline.com/showThread.cfm?link=286222 about this… very thought provoking… so i think i have got this right… i can support windows 10 iot enterprise in a consistent sort of a way with existing drivers if i decide to not go “Universal” and stick with the desktop model… this seems kinda perverse… but hey ho…

xxxxx@gmail.com wrote:

peter v - i read your thoughts in this thread http://www.osronline.com/showThread.cfm?link=286222 about this… very thought provoking… so i think i have got this right… i can support windows 10 iot enterprise in a consistent sort of a way with existing drivers if i decide to not go “Universal” and stick with the desktop model… this seems kinda perverse… but hey ho…

For hardware drivers, it’s not that perverse.  You don’t find many
phones and tables with PCIe slots, for example.  :wink:


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.


For hardware drivers, it’s not that perverse.  You don’t find many
phones and tables with PCIe slots, for example.  :wink:

Not all embedded is phones/tablets. You might also be surprised how many embedded devices use PCIe hard-wired to devices that are not removable as in traditional PCIe implementation. They are still PCIe devices, require PCIe stack and enumeration/configuration.

Greg

Yes, but embedded isn?t phones or tablets. Phones are ?mobile? and tablets are… well… it depends.

But IoT enterprise is ?desktop??clear as mud, right?

Thank you, Mr. Lockard, for that clarification. The whole ?U? requirement has been ?backed off? so many times, I?ve lost track.

Would you be kind enough to explain to me what the thinking is behind not allowing ClassInstall32? Nobody has explained this to me, and I?d love to know what I?m missing. Because I see not supporting it as a BIG problem.

Peter
OSR
@OSRDrivers

>For hardware drivers, it’s not that perverse.  You don’t find many phones

and tables with PCIe slots, for example. 

I could imagine a tablet or phone with a USB-C connector that supports Thunderbolt 3, which is basically PCIe on a tiny connector.

Jan

The short explanation is that declaring it to be universal means that we’ll have to support it in all cases, and there is concern on our end about making that guarantee for ClassInstall32. Given that classes are created in their own namespace, separate from any other driver information (global keys under CCS\Control\Class<guid>), changes to how drivers are added to the system may necessitate separate work to enable ClassInstall32. Specifically, any sort of work that would encapsulate all driver state into a single location, similar to the HKR registry root, would preclude ClassInstall32. You could say the same about device services and interfaces, but we’ve got a mechanism to sort of “cache” this global state into the driver database, and reflect it out to these global locations when the device becomes present. A similar mechanism would need to be created for classes before we’d be able to make class definitions universal.

-----Original Message-----
From: xxxxx@lists.osr.com On Behalf Of xxxxx@osr.com
Sent: Thursday, June 7, 2018 7:35 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] inf files - ClassInstall32 now banned?



Yes, but embedded isn?t phones or tablets. Phones are ?mobile? and tablets are… well… it depends.

But IoT enterprise is ?desktop??clear as mud, right?



Thank you, Mr. Lockard, for that clarification. The whole ?U? requirement has been ?backed off? so many times, I?ve lost track.

Would you be kind enough to explain to me what the thinking is behind not allowing ClassInstall32? Nobody has explained this to me, and I?d love to know what I?m missing. Because I see not supporting it as a BIG problem.

Peter
OSR
@OSRDrivers


NTDEV is sponsored by OSR

Visit the list online at: https:

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at https:

To unsubscribe, visit the List Server section of OSR Online at https:</https:></https:></https:>

Thank you, Mr. Lockard. I appreciate the explanation. I was sure there was a reason.

I speak for a lot of IHVs when I says that I hope you folks re-visit the work required to support ClassInstall32 and consider it worthwhile. But, in any case, thanks again for the reply.

Peter
OSR
@OSRDrivers