Root enumerated device doesn't survive from OS upgrade

Hi,

I wrote a PnP software only functional driver using WDM, used DIF_REGISTERDEVICE to install the driver (e.g. devcon install myvirtual.inf myvirtual). I noticed the root enumerated device didn’t get populated in new OS when I upgraded OS from WS08 to WS08 R2. The driver is WHQL signed.

Is this an known issue to anyone?

Regards,
JT

By design. Starting with Vista, an OS to OS upgrade is a clean install with migration of settings, root enumerated devices are not migrated

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@emc.com
Sent: Monday, October 25, 2010 12:27 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Root enumerated device doesn’t survive from OS upgrade

Hi,

I wrote a PnP software only functional driver using WDM, used DIF_REGISTERDEVICE to install the driver (e.g. devcon install myvirtual.inf myvirtual). I noticed the root enumerated device didn’t get populated in new OS when I upgraded OS from WS08 to WS08 R2. The driver is WHQL signed.

Is this an known issue to anyone?

Regards,
JT


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

Doron,

Would you please comment then on the handling of ‘upgrade’ as it relates to
third-party applications installed, say, with Windows Installer?

Are these migrated by re-installing them (and thus, if drivers are installed
with DIFxAPP, re-installed) or are they dropped on the floor during this
process?

Thanks,
Dave Cattley

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Monday, October 25, 2010 6:07 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Root enumerated device doesn’t survive from OS upgrade

By design. Starting with Vista, an OS to OS upgrade is a clean install with
migration of settings, root enumerated devices are not migrated

d

Last time I was checking Vista to 7 upgrade it was working for services
installed via MSI and difxapp.


Volodymyr

“David R. Cattley” a écrit dans le message de groupe de
discussion : xxxxx@ntdev…
> Doron,
>
> Would you please comment then on the handling of ‘upgrade’ as it relates
> to
> third-party applications installed, say, with Windows Installer?
>
> Are these migrated by re-installing them (and thus, if drivers are
> installed
> with DIFxAPP, re-installed) or are they dropped on the floor during this
> process?
>
> Thanks,
> Dave Cattley
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
> Sent: Monday, October 25, 2010 6:07 PM
> To: Windows System Software Devs Interest List
> Subject: RE: [ntdev] Root enumerated device doesn’t survive from OS
> upgrade
>
> By design. Starting with Vista, an OS to OS upgrade is a clean install
> with
> migration of settings, root enumerated devices are not migrated
>
> d
>
>

That’s an another surprise coming from Microsoft. You follow Microsoft’s recommendation to write a software only PnP driver for your virtual device, and the method documented in WDK to install the driver. It gets dropped on the floor during OS upgrade ?!

Will Microsft take special care of the third party DSM drivers for MPIO, storage virtual miniport drivers?

JT.

IIRC, if you install via MSI / difx, you get reinstalled. OTOH, the number of OS upgrades is extremely miniscule compared to clean installs, esp in the server environment.

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@emc.com
Sent: Wednesday, October 27, 2010 8:27 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Root enumerated device doesn’t survive from OS upgrade

That’s an another surprise coming from Microsoft. You follow Microsoft’s recommendation to write a software only PnP driver for your virtual device, and the method documented in WDK to install the driver. It gets dropped on the floor during OS upgrade ?!

Will Microsft take special care of the third party DSM drivers for MPIO, storage virtual miniport drivers?

JT.


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

>driver. It gets dropped on the floor during OS upgrade ?!

I think I would not disclose you any major secret if I will say you: Windows OS upgrades never ever worked.

The chances of running this procedure and getting all 3rd party software working after it are next to zero. It will surely introduce issues to 3rd party software.

I personally never saw any person successful in doing Windows OS upgrade. All people I know who tried this have spitting around and making oathes “I will never do this the second time!”.

Clean reinstall of Windows, followed by clean reinstall of all 3rd party software, is the only chance and is faster then the attempt to repair the broken software titles after the OS upgrade.

As about your case - you will need to write and releate the post-upgrade EXE which will call the proper SetupDi functions to restore your device, and suggest everybody running the clumsy procedure of Windows upgrade to run this EXE after.


Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com