Partmgr bug still happening after W10 RS2

Hi folks,

Last year I came across an issue with my upper filter for disk devices and Windows 10 RS2 (version 1703), I posted the case here (https://www.osronline.com/showthread.cfm?link=284817) and after some research from myself and other guys, it was Mr Scott Noone from OSR who came to the conclusion that there was some sort of race condition bug in Partmgr, specifically in PmSendTelemetry function.

I was hoping that Microsoft might fix it in further revisions, but I am testing right now in a Win10 version 1709 (build 17025.1000, an Insiders Preview version) and the problem is still there.

So maybe someone from MS might shed some light about the issue and maybe confirm if they plan to fix it, or at least advise some workaround, not involving the removal of DriverUnload function.

Thanks!

Send feedback with the feedback hub. A hope and a prayer that someone sees it here and acts on it is not the right choice.

d

Bent from my phone


From: xxxxx@lists.osr.com on behalf of xxxxx@teleline.es
Sent: Tuesday, February 13, 2018 7:16:47 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Partmgr bug still happening after W10 RS2

Hi folks,

Last year I came across an issue with my upper filter for disk devices and Windows 10 RS2 (version 1703), I posted the case here (https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.osronline.com%2Fshowthread.cfm%3Flink%3D284817&data=04|01|Doron.Holan%40microsoft.com|3f935dd0d2524e07bf1c08d572f4cf8b|72f988bf86f141af91ab2d7cd011db47|1|0|636541318137577994|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&sdata=6XN44J8c6z9WpPcgTBb%2FttNBT%2Bo3zRq51MVpH9CKAT0%3D&reserved=0) and after some research from myself and other guys, it was Mr Scott Noone from OSR who came to the conclusion that there was some sort of race condition bug in Partmgr, specifically in PmSendTelemetry function.

I was hoping that Microsoft might fix it in further revisions, but I am testing right now in a Win10 version 1709 (build 17025.1000, an Insiders Preview version) and the problem is still there.

So maybe someone from MS might shed some light about the issue and maybe confirm if they plan to fix it, or at least advise some workaround, not involving the removal of DriverUnload function.

Thanks!


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 Doron, I just filled a Feedback request at the Collaborate section in developer Dashboard.

Thanks!

In an ironic twist, your feedback bug was routed to my team today ;). I moved it along to the partmgr team.

d

Bent from my phone


From: Doron Holan
Sent: Tuesday, February 13, 2018 7:35:38 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Partmgr bug still happening after W10 RS2

Send feedback with the feedback hub. A hope and a prayer that someone sees it here and acts on it is not the right choice.

d

Bent from my phone


From: xxxxx@lists.osr.com on behalf of xxxxx@teleline.es
Sent: Tuesday, February 13, 2018 7:16:47 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Partmgr bug still happening after W10 RS2

Hi folks,

Last year I came across an issue with my upper filter for disk devices and Windows 10 RS2 (version 1703), I posted the case here (https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.osronline.com%2Fshowthread.cfm%3Flink%3D284817&amp;data=04|01|Doron.Holan%40microsoft.com|3f935dd0d2524e07bf1c08d572f4cf8b|72f988bf86f141af91ab2d7cd011db47|1|0|636541318137577994|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&amp;sdata=6XN44J8c6z9WpPcgTBb%2FttNBT%2Bo3zRq51MVpH9CKAT0%3D&amp;reserved=0) and after some research from myself and other guys, it was Mr Scott Noone from OSR who came to the conclusion that there was some sort of race condition bug in Partmgr, specifically in PmSendTelemetry function.

I was hoping that Microsoft might fix it in further revisions, but I am testing right now in a Win10 version 1709 (build 17025.1000, an Insiders Preview version) and the problem is still there.

So maybe someone from MS might shed some light about the issue and maybe confirm if they plan to fix it, or at least advise some workaround, not involving the removal of DriverUnload function.

Thanks!


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:>