Domain GPO removes USB-C docks driver under Win10
First a little background.
I have a Dell Precision 7510 laptop @ work, connected to a Dell WD15 connected via USB-C.
- Microsoft Windows 10 Enterprise
- Version 10.0.15063 Build 15063
- System Type x64-based PC
My problem is that when connected to the dock, everything working, all of a sudden, the dock is removed, and drivers need to be manually installed, to get it working again.
I have been looking into the problem, and believe rooted cause to be my companies group policies, pushed via the domain, but I have thus fare not been able to get them to fix it, and I am therefore exploring if other options are available.
I have been investigating the event log when the dock is thrown offline, and found that it all starts with an GPO update:
Then right after, the device is deleted:
The the device throws an error:
Then an info that the device requires further installation:
Then an info that driver install failed with code 0xE0000248:
To my knowledge, this code 0xE0000248 reads:
The installation of this device is forbidden by system policy.
This is what lead me to believe that GPO were to blame, and after some digging, I found:
and when examining the "PCI to PCI Bridge" properties, I found this list of compatibles ID's for the hardware:
Based on the fact that "PCICC_0C0A" are mentioned in both, I believe the removal are triggered by the GPO. If anyone has reason to disagree with my conclusion, kindly say so, with explanation why.
At long last, my question. I am interested in knowing from where the list of compatible ID's comes?
Case #1:
When windows detects a new device, the device informs this list to windows, which then tries to locate an appropriate driver based on the list.
Case #2:
The list somehow comes from windows and/or driver inf files, and windows then tries to locate an appropriate driver based on the list.
Case #3:
Something completely different?
If #2 is what happens, is there then a way for me to remove "PCICC_0C0A" from the list of compatible ID's, thereby hopefully preventing the GPO from removing the dock?
Thanks in advance.
Best Regards
Henrik V. Nielsen
windows-10 drivers group-policy
asked Dec 6 '17 at 8:10
Henrik Nielsen
345
add a comment |
First a little background.
I have a Dell Precision 7510 laptop @ work, connected to a Dell WD15 connected via USB-C.
- Microsoft Windows 10 Enterprise
- Version 10.0.15063 Build 15063
- System Type x64-based PC
My problem is that when connected to the dock, everything working, all of a sudden, the dock is removed, and drivers need to be manually installed, to get it working again.
I have been looking into the problem, and believe rooted cause to be my companies group policies, pushed via the domain, but I have thus fare not been able to get them to fix it, and I am therefore exploring if other options are available.
I have been investigating the event log when the dock is thrown offline, and found that it all starts with an GPO update:
Then right after, the device is deleted:
The the device throws an error:
Then an info that the device requires further installation:
Then an info that driver install failed with code 0xE0000248:
To my knowledge, this code 0xE0000248 reads:
The installation of this device is forbidden by system policy.
This is what lead me to believe that GPO were to blame, and after some digging, I found:
and when examining the "PCI to PCI Bridge" properties, I found this list of compatibles ID's for the hardware:
Based on the fact that "PCICC_0C0A" are mentioned in both, I believe the removal are triggered by the GPO. If anyone has reason to disagree with my conclusion, kindly say so, with explanation why.
At long last, my question. I am interested in knowing from where the list of compatible ID's comes?
Case #1:
When windows detects a new device, the device informs this list to windows, which then tries to locate an appropriate driver based on the list.
Case #2:
The list somehow comes from windows and/or driver inf files, and windows then tries to locate an appropriate driver based on the list.
Case #3:
Something completely different?
If #2 is what happens, is there then a way for me to remove "PCICC_0C0A" from the list of compatible ID's, thereby hopefully preventing the GPO from removing the dock?
Thanks in advance.
Best Regards
Henrik V. Nielsen
windows-10 drivers group-policy
asked Dec 6 '17 at 8:10
Henrik Nielsen
345
add a comment |
First a little background.
I have a Dell Precision 7510 laptop @ work, connected to a Dell WD15 connected via USB-C.
- Microsoft Windows 10 Enterprise
- Version 10.0.15063 Build 15063
- System Type x64-based PC
My problem is that when connected to the dock, everything working, all of a sudden, the dock is removed, and drivers need to be manually installed, to get it working again.
I have been looking into the problem, and believe rooted cause to be my companies group policies, pushed via the domain, but I have thus fare not been able to get them to fix it, and I am therefore exploring if other options are available.
I have been investigating the event log when the dock is thrown offline, and found that it all starts with an GPO update:
Then right after, the device is deleted:
The the device throws an error:
Then an info that the device requires further installation:
Then an info that driver install failed with code 0xE0000248:
To my knowledge, this code 0xE0000248 reads:
The installation of this device is forbidden by system policy.
This is what lead me to believe that GPO were to blame, and after some digging, I found:
and when examining the "PCI to PCI Bridge" properties, I found this list of compatibles ID's for the hardware:
Based on the fact that "PCICC_0C0A" are mentioned in both, I believe the removal are triggered by the GPO. If anyone has reason to disagree with my conclusion, kindly say so, with explanation why.
At long last, my question. I am interested in knowing from where the list of compatible ID's comes?
Case #1:
When windows detects a new device, the device informs this list to windows, which then tries to locate an appropriate driver based on the list.
Case #2:
The list somehow comes from windows and/or driver inf files, and windows then tries to locate an appropriate driver based on the list.
Case #3:
Something completely different?
If #2 is what happens, is there then a way for me to remove "PCICC_0C0A" from the list of compatible ID's, thereby hopefully preventing the GPO from removing the dock?
Thanks in advance.
Best Regards
Henrik V. Nielsen
windows-10 drivers group-policy
asked Dec 6 '17 at 8:10
Henrik Nielsen
345
First a little background.
I have a Dell Precision 7510 laptop @ work, connected to a Dell WD15 connected via USB-C.
- Microsoft Windows 10 Enterprise
- Version 10.0.15063 Build 15063
- System Type x64-based PC
My problem is that when connected to the dock, everything working, all of a sudden, the dock is removed, and drivers need to be manually installed, to get it working again.
I have been looking into the problem, and believe rooted cause to be my companies group policies, pushed via the domain, but I have thus fare not been able to get them to fix it, and I am therefore exploring if other options are available.
I have been investigating the event log when the dock is thrown offline, and found that it all starts with an GPO update:
Then right after, the device is deleted:
The the device throws an error:
Then an info that the device requires further installation:
Then an info that driver install failed with code 0xE0000248:
To my knowledge, this code 0xE0000248 reads:
The installation of this device is forbidden by system policy.
This is what lead me to believe that GPO were to blame, and after some digging, I found:
and when examining the "PCI to PCI Bridge" properties, I found this list of compatibles ID's for the hardware:
Based on the fact that "PCICC_0C0A" are mentioned in both, I believe the removal are triggered by the GPO. If anyone has reason to disagree with my conclusion, kindly say so, with explanation why.
At long last, my question. I am interested in knowing from where the list of compatible ID's comes?
Case #1:
When windows detects a new device, the device informs this list to windows, which then tries to locate an appropriate driver based on the list.
Case #2:
The list somehow comes from windows and/or driver inf files, and windows then tries to locate an appropriate driver based on the list.
Case #3:
Something completely different?
If #2 is what happens, is there then a way for me to remove "PCICC_0C0A" from the list of compatible ID's, thereby hopefully preventing the GPO from removing the dock?
Thanks in advance.
Best Regards
Henrik V. Nielsen
windows-10 drivers group-policy
windows-10 drivers group-policy
asked Dec 6 '17 at 8:10
Henrik Nielsen
345
asked Dec 6 '17 at 8:10
Henrik Nielsen
345
asked Dec 6 '17 at 8:10
Henrik Nielsen
345
asked Dec 6 '17 at 8:10
Henrik Nielsen
345
asked Dec 6 '17 at 8:10
Henrik Nielsen
345
345
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This is not so much an answer, as my current workaround.
Therefore my original question, how to prevent the USB-C dock from registering "PCICC_0C0A" as a compatible device ID, still remains. If possible?
Update
The disconnect happened a lot of time during a normal work day, and required me to manually reinstall 4 drivers to get it up and running again.
I have successfully created a script to ease the problem.
The script does the following:
- Elevates itself to administrator (based on a script found in a post on this site)
- Enables policy "Turn off background refresh of GPO", by adding "DisableBkGndGroupPolicy" in registry
- Delete the offending company GPO from registry
- Elevate the script to TrustedInstaller (3 party program called PowerRun)
- Delete all traces of old USB dock drivers from registry (found that they sometimes generated problems)
- This leaves a disconnect and reconnect of the USB-C to be performed by me
In the morning, the GPO always find a way to update (does not happen when rebooting during the day, weird), but above usually dropping the need to re-install to that one time. Also the only action required by me is to disconnect and reconnect the USB-C once the script has been executed.
answered Dec 20 '17 at 12:20
Henrik Nielsen
345
This is really a comment and not an answer to the original question. You can always comment on your own posts, and once you have sufficient reputation you will be able to comment on any post. Please read Why do I need 50 reputation to comment? What can I do instead?
– DavidPostill♦
Dec 13 '18 at 20:32
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1274709%2fdomain-gpo-removes-usb-c-docks-driver-under-win10%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is not so much an answer, as my current workaround.
Therefore my original question, how to prevent the USB-C dock from registering "PCICC_0C0A" as a compatible device ID, still remains. If possible?
Update
The disconnect happened a lot of time during a normal work day, and required me to manually reinstall 4 drivers to get it up and running again.
I have successfully created a script to ease the problem.
The script does the following:
- Elevates itself to administrator (based on a script found in a post on this site)
- Enables policy "Turn off background refresh of GPO", by adding "DisableBkGndGroupPolicy" in registry
- Delete the offending company GPO from registry
- Elevate the script to TrustedInstaller (3 party program called PowerRun)
- Delete all traces of old USB dock drivers from registry (found that they sometimes generated problems)
- This leaves a disconnect and reconnect of the USB-C to be performed by me
In the morning, the GPO always find a way to update (does not happen when rebooting during the day, weird), but above usually dropping the need to re-install to that one time. Also the only action required by me is to disconnect and reconnect the USB-C once the script has been executed.
answered Dec 20 '17 at 12:20
Henrik Nielsen
345
This is really a comment and not an answer to the original question. You can always comment on your own posts, and once you have sufficient reputation you will be able to comment on any post. Please read Why do I need 50 reputation to comment? What can I do instead?
– DavidPostill♦
Dec 13 '18 at 20:32
add a comment |
This is not so much an answer, as my current workaround.
Therefore my original question, how to prevent the USB-C dock from registering "PCICC_0C0A" as a compatible device ID, still remains. If possible?
Update
The disconnect happened a lot of time during a normal work day, and required me to manually reinstall 4 drivers to get it up and running again.
I have successfully created a script to ease the problem.
The script does the following:
- Elevates itself to administrator (based on a script found in a post on this site)
- Enables policy "Turn off background refresh of GPO", by adding "DisableBkGndGroupPolicy" in registry
- Delete the offending company GPO from registry
- Elevate the script to TrustedInstaller (3 party program called PowerRun)
- Delete all traces of old USB dock drivers from registry (found that they sometimes generated problems)
- This leaves a disconnect and reconnect of the USB-C to be performed by me
In the morning, the GPO always find a way to update (does not happen when rebooting during the day, weird), but above usually dropping the need to re-install to that one time. Also the only action required by me is to disconnect and reconnect the USB-C once the script has been executed.
answered Dec 20 '17 at 12:20
Henrik Nielsen
345
This is really a comment and not an answer to the original question. You can always comment on your own posts, and once you have sufficient reputation you will be able to comment on any post. Please read Why do I need 50 reputation to comment? What can I do instead?
– DavidPostill♦
Dec 13 '18 at 20:32
add a comment |
This is not so much an answer, as my current workaround.
Therefore my original question, how to prevent the USB-C dock from registering "PCICC_0C0A" as a compatible device ID, still remains. If possible?
Update
The disconnect happened a lot of time during a normal work day, and required me to manually reinstall 4 drivers to get it up and running again.
I have successfully created a script to ease the problem.
The script does the following:
- Elevates itself to administrator (based on a script found in a post on this site)
- Enables policy "Turn off background refresh of GPO", by adding "DisableBkGndGroupPolicy" in registry
- Delete the offending company GPO from registry
- Elevate the script to TrustedInstaller (3 party program called PowerRun)
- Delete all traces of old USB dock drivers from registry (found that they sometimes generated problems)
- This leaves a disconnect and reconnect of the USB-C to be performed by me
In the morning, the GPO always find a way to update (does not happen when rebooting during the day, weird), but above usually dropping the need to re-install to that one time. Also the only action required by me is to disconnect and reconnect the USB-C once the script has been executed.
answered Dec 20 '17 at 12:20
Henrik Nielsen
345
This is not so much an answer, as my current workaround.
Therefore my original question, how to prevent the USB-C dock from registering "PCICC_0C0A" as a compatible device ID, still remains. If possible?
Update
The disconnect happened a lot of time during a normal work day, and required me to manually reinstall 4 drivers to get it up and running again.
I have successfully created a script to ease the problem.
The script does the following:
- Elevates itself to administrator (based on a script found in a post on this site)
- Enables policy "Turn off background refresh of GPO", by adding "DisableBkGndGroupPolicy" in registry
- Delete the offending company GPO from registry
- Elevate the script to TrustedInstaller (3 party program called PowerRun)
- Delete all traces of old USB dock drivers from registry (found that they sometimes generated problems)
- This leaves a disconnect and reconnect of the USB-C to be performed by me
In the morning, the GPO always find a way to update (does not happen when rebooting during the day, weird), but above usually dropping the need to re-install to that one time. Also the only action required by me is to disconnect and reconnect the USB-C once the script has been executed.
answered Dec 20 '17 at 12:20
Henrik Nielsen
345
edited Dec 22 '17 at 6:40
answered Dec 20 '17 at 12:20
Henrik Nielsen
345
answered Dec 20 '17 at 12:20
Henrik Nielsen
345
answered Dec 20 '17 at 12:20
Henrik Nielsen
345
345
This is really a comment and not an answer to the original question. You can always comment on your own posts, and once you have sufficient reputation you will be able to comment on any post. Please read Why do I need 50 reputation to comment? What can I do instead?
– DavidPostill♦
Dec 13 '18 at 20:32
add a comment |
This is really a comment and not an answer to the original question. You can always comment on your own posts, and once you have sufficient reputation you will be able to comment on any post. Please read Why do I need 50 reputation to comment? What can I do instead?
– DavidPostill♦
Dec 13 '18 at 20:32
This is really a comment and not an answer to the original question. You can always comment on your own posts, and once you have sufficient reputation you will be able to comment on any post. Please read Why do I need 50 reputation to comment? What can I do instead?
– DavidPostill♦
Dec 13 '18 at 20:32
This is really a comment and not an answer to the original question. You can always comment on your own posts, and once you have sufficient reputation you will be able to comment on any post. Please read Why do I need 50 reputation to comment? What can I do instead?
– DavidPostill♦
Dec 13 '18 at 20:32
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1274709%2fdomain-gpo-removes-usb-c-docks-driver-under-win10%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
