Cannot access USB drive
-
@Dashrender said in Cannot access USB drive:
Time to take a snap of the registry, then apply the change, then compare them.
It is already broke. that will not find a change.
-
@JaredBusch said in Cannot access USB drive:
@Dashrender said in Cannot access USB drive:
Time to take a snap of the registry, then apply the change, then compare them.
It is already broke. that will not find a change.
my bad - I meant get a new machine/image, snap before applied.. then apply snap again and compare.
-
@JaredBusch said in Cannot access USB drive:
I'm all out of ideas..
Try with Rufus on that same device.
-
@JaredBusch said in Cannot access USB drive:
HKLM\SOFTWARE\Microsoft\PolicyManager\current\device\System
Name: AllowStorageCard@JaredBusch This link is based on XP and 2003 but can't hurt to compare to a working Windows 10 computer with the computer that is working correctly?
https://support.microsoft.com/en-us/help/823732/how-can-i-prevent-users-from-connecting-to-a-usb-storage-device -
I know I am late but this is probably what you are experiencing
https://microsoftintune.uservoice.com/forums/291681-ideas/suggestions/35053123-have-windows-revert-to-default-settings-when-windo -
-
@dbeato said in Cannot access USB drive:
@dbeato supposedly this is a workaround
https://social.technet.microsoft.com/Forums/en-US/a93b2214-48da-4dbd-89cd-a6b5ef77369f/resetting-device-profiles-without-retiring-device?forum=microsoftintuneprodYeah, I was already assuming that, but I've checked every setting I can find related to USB access and made sure they were opened again.
-
@JaredBusch I gotta test with my labs VMs and report findings later.
-
I still have no luck with this and I cannot find any settings that make any sense.
I've become good friends with CreenConnect's command screen.
#!ps #maxlength=50000 #timeout=300000 Get-ChildItem -Path HKLM:\SOFTWARE\Microsoft\PolicyManager\default Get-ChildItem -Path HKLM:\SOFTWARE\Microsoft\PolicyManager\current\device Get-ChildItem -Path HKLM:\SOFTWARE\Microsoft\PolicyManager\Providers\1e05dd5d-a022-46c5-963c-b20de341170f\default\device Get-ChildItem -Path HKLM:\SOFTWARE\Microsoft\PolicyManager\Providers\2648BF76-DA4B-409A-BFFA-6AF111C298A5\default\device Get-ChildItem -Path HKLM:\SOFTWARE\Microsoft\PolicyManager\Providers\27A6435B-4F98-4B0C-9EE6-6D2B5A0C7879\default\device Get-ChildItem -Path HKLM:\SOFTWARE\Microsoft\PolicyManager\Providers\8d196d7f-3eef-48ad-8bea-be749f12d3ad\default\device Get-ChildItem -Path HKLM:\SOFTWARE\Microsoft\PolicyManager\Providers\8fb7d64e-70fc-4f9d-89ee-d486817534df\default\device Get-ChildItem -Path HKLM:\SOFTWARE\Microsoft\PolicyManager\Providers\fc01e91f-914c-45af-9d7c-0b2e5fbedf62\default\device
-
Since the registry seems to be the pain-point, as much as they may be looked down upon by lots of the folks here, have you tried any of the registry "cleaner" tools? Ccleaner and Wise365 both have portable versions and they both allow you to run an analysis without applying any changes.
-
@JaredBusch - have you had any luck? I've not had to lock USB down here (yet), but I have had issues with Intune configuration policy (re)application and general "fuzziness". I've been keeping an eye on this thread.
I will second @notverypunny on the register cleaner tools sometimes being a possible help. I have to deploy Office 2019 here (MS punish Admins who haven't been able to acquire click-to-run product licencing, with this product :confounded_face: ). Some install errors were fixed with registry cleanup provided by a portable version of a mentioned application.
-
Just out of interest. Did anyone find the answer to your problem? We are having the exact same problem in a production environment. A device had the Intune USB block policy enabled and trying to reverse it has been a pain with no luck.
-
@Super-Sundae said in Cannot access USB drive:
Just out of interest. Did anyone find the answer to your problem? We are having the exact same problem in a production environment. A device had the Intune USB block policy enabled and trying to reverse it has been a pain with no luck.
I still have not
-
@Super-Sundae : Can you run Sysinternal's RegMon and patch another machine with InTune? That way you can capture the changes.
Perhaps running SysMon at the same time in case it makes changes to file permissions would help..If you can find out what the policy changes then you should be able to revert on both machines. Hopefully
