-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -

Create an account on the HP Community to personalize your profile and ask a question
06-09-2026 05:41 PM
not recognized all cabels are correct and working.. ideas
Solved! Go to Solution.
Accepted Solutions
06-13-2026 02:42 PM
Hi @JT33040,
Thank you for the update and for taking the time to work through the recommendations. I appreciate you sharing your findings.
From your description, it sounds like you've spent quite a bit of time testing the UEFI-related options and have already tried multiple approaches without success. Sometimes the simplest issues can indeed lead to the most unexpected troubleshooting results.
Since you mentioned this is related to the camera issue and the behavior appears to have started after recent system changes, one thing we could try is restoring the PC to a point when the camera was working correctly.
System Restore does not affect your personal files, but it can revert system settings, drivers, and updates that may have contributed to the issue.
To perform a System Restore:
- In Windows, search for Create a restore point and open it.
- Click System Restore.
- Select a restore point from a date when the camera was functioning properly.
- Follow the prompts to complete the restore process.
- Once the PC restarts, test the camera again.
If a suitable restore point is available, this can be a quick way to determine whether the issue is software-related.
Please let us know if you're able to perform the restore and whether the camera behavior changes afterwards. We'll be happy to continue working with you based on the results.
I'm an HP Employee.
If this reply helped resolve your issue, please select the Accept as Solution as it helps others in the community quickly find the answer they’re looking for.
And if you found this reply helpful, clicking Yes below is a great way to let us know we’re providing the support you need, as it encourages us to keep improving and sharing helpful guidance.
06-11-2026 07:39 AM
Hi @JT33040,
Welcome to the HP Support Community.
Thank you for posting your query. I will be glad to help you.
Thank you for reaching out. I'd be happy to help, but I need a bit more information to understand better the issue you're experiencing.
When you mention "not recognized", could you please elaborate on what exactly is not being recognized?
- Is it a printer, monitor, USB device, hard drive, docking station, or another component?
- Are you receiving any specific error messages?
- Does the issue occur when the device is connected to a particular port or cable?
Since you've already confirmed that the cables are connected correctly and are working, it would be very helpful if you could share:
- The exact HP model of the device you're using.
- A photo or screenshot of the error message (if one is displayed).
- Details about what you're trying to connect and what behavior you're seeing.
Once we have a better understanding of the issue and can review any error messages or images, we'll be in a much better position to help troubleshoot and identify the cause.
Take care and have an amazing day!
I'm an HP Employee.
If this reply helped resolve your issue, please select the Accept as Solution as it helps others in the community quickly find the answer they’re looking for.
And if you found this reply helpful, clicking Yes below is a great way to let us know we’re providing the support you need, as it encourages us to keep improving and sharing helpful guidance.
06-11-2026 07:25 PM
Thanks much for the response.. what I have going on is with my HP Notebook- 15-da2002ca and the device that I am referring to isn the preinstalled Webcam, which is the True Vision 720 HD camera with intragated digital microphone. Current OS is Win 11 Home . Aprox 2 weeks ago or so had an accident, and hard drive got wet and well, we know what happened. That said, I had another HP and was able to swap out some of the componets and here is stand with a fantastic product without the webcam. I do have an external usb cam that I had been ( using, but after much devotion and stubbornness, I was able to research and have found that the or6/10/2026 6:35:18 AM
iginal camera, preinstalled seems to be in the device manager if I search.. but only to find it under eitehr camera, which it is not listed as the camera I am looking for but rather just the USB external camera. That said further on down i will have the USB serial and it is throwing an error.. stating
Device settings for USB\VID_0000&PID_0001\5&1c89cdc0&0&16 were migrated from previous OS installation.
Last Device Instance ID: USB\VID_0000&PID_0001\5&1c89cdc0&0&16
Class GUID: {36fc9e60-c465-11cf-8056-444553540000}
Location Path:
Migration Rank: 0x0
Present: true
at a different time i was able to find or well let me see if I can recreate..
This is what i get when I plug in the usb camera .. also now in DM i have camera listed.. but only is the usb camera.. I have done the update.. the roll back everything except for reinstalling the driver for the HP True Vision 720 HD...
Device settings for USB\VID_0000&PID_0001\5&1c89cdc0&0&16 were migrated from previous OS installation.
Last Device Instance ID: USB\VID_0000&PID_0001\5&1c89cdc0&0&16
Class GUID: {36fc9e60-c465-11cf-8056-444553540000}
Location Path:
Migration Rank: 0x0
Present: true
Device settings for USB\VID_0000&PID_0001\5&1c89cdc0&0&16 were migrated from previous OS installation.
Last Device Instance ID: USB\VID_0000&PID_0001\5&1c89cdc0&0&16
Class GUID: {36fc9e60-c465-11cf-8056-444553540000}
Location Path:
Migration Rank: 0x0
Present: true
Device USB\VID_048E&PID_0880&MI_00\6&23884205&0&0000 requires further installation.
This appears when i have the usb plugged in. I apologize for being all over the place here but kinda how my brain works.. This message also gives me the hope that it will be an easy fix by just installing the driver ? Bouncing reading and many late nights..
As for cables, my apologies.. that referred to the camera wiring/harness that is attached.. Yes I have made some adjustments and changes but all has been done on the most extreme err of caution. during all of this and there was a program that was run for idk what I think in bios or something and it tried to locate preinstalled cam and well it did.. and then it said immediately that there was none installed.
Trying to think of the other error that, is well a common one that I have seen in discussion about there being no camera installed and ......
06-11-2026 08:37 PM
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 6/10/2026 6:37:24 AM
Event ID: 400
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: JTUpdated
Description:
Device USB\VID_0000&PID_0001\5&1c89cdc0&0&16 was configured.
Driver Name: usb.inf
Driver Package ID: usb.inf_amd64_a10c4ca0f120b7f5
Class GUID: {36fc9e60-c465-11cf-8056-444553540000}
Driver Date: 06/21/2006
Driver Version: 10.0.26100.8521
Driver Provider: Microsoft
Driver Section: BADDEVICE.Dev.NT
Driver Rank: 0xFF0000
Matching Device ID: USB\RESET_FAILURE
Outranked Drivers: usb.inf:USB\RESET_FAILURE:00FF2000
Device Updated: false
Parent Device: USB\ROOT_HUB30\4&314c960f&0&0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9c205a39-1250-487d-abd7-e831c6290539}" />
<EventID>400</EventID>
<Version>1</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2026-06-10T11:37:24.1468592Z" />
<EventRecordID>534</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="436" />
<Channel>Microsoft-Windows-Kernel-PnP/Configuration</Channel>
<Computer>JTUpdated</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="DeviceInstanceId">USB\VID_0000&PID_0001\5&1c89cdc0&0&16</Data>
<Data Name="DriverName">usb.inf</Data>
<Data Name="ClassGuid">{36fc9e60-c465-11cf-8056-444553540000}</Data>
<Data Name="DriverDate">06/21/2006</Data>
<Data Name="DriverVersion">10.0.26100.8521</Data>
<Data Name="DriverProvider">Microsoft</Data>
<Data Name="DriverInbox">true</Data>
<Data Name="DriverSection">BADDEVICE.Dev.NT</Data>
<Data Name="DriverRank">0xff0000</Data>
<Data Name="MatchingDeviceId">USB\RESET_FAILURE</Data>
<Data Name="OutrankedDrivers">usb.inf:USB\RESET_FAILURE:00FF2000</Data>
<Data Name="DeviceUpdated">false</Data>
<Data Name="Status">0x0</Data>
<Data Name="ParentDeviceInstanceId">USB\ROOT_HUB30\4&314c960f&0&0</Data>
<Data Name="DriverPackageId">usb.inf_amd64_a10c4ca0f120b7f5</Data>
</EventData>
</Event>
06-12-2026 12:35 PM
Hi @JT33040,
Thank you for taking the time to provide such a detailed explanation. I can definitely follow what you're describing, and the additional information is very helpful.
From what you've shared, a few things stand out:
- The notebook is an HP Notebook - 15-da2002ca running Windows 11 Home.
- The original hard drive was damaged after getting wet, and some components were transferred from another HP system.
- The HP TrueVision HD Camera is no longer being detected normally.
- The external USB camera is detected, but the integrated camera is not.
- The Event Viewer logs are showing entries such as USB\RESET_FAILURE and BADDEVICE.Dev.NT, which indicates that Windows is detecting a USB device communication failure rather than a normal camera device.
What concerns me most is the statement that a utility previously attempted to detect the integrated camera and immediately reported that no camera was installed. Combined with the USB reset failure entries, this points away from a simple camera application issue.
At this point, I'd recommend checking the hardware side before spending more time on driver troubleshooting.
1. Run HP Hardware Diagnostics
- Shut down the notebook.
- Turn it back on and repeatedly tap F2.
- Open HP PC Hardware Diagnostics UEFI.
- Run the available Component Tests and check whether a Camera test is available.
- If any test fails, please note the Failure ID.
2. Perform an HP BIOS Recovery
Since hardware changes were made and Windows 11 was installed afterwards, let's also refresh the BIOS configuration:
- Turn the notebook off.
- Connect the AC adapter.
- Press and hold Windows + B.
- Press and hold the Power button for 2–3 seconds.
- Release the Power button while continuing to hold Windows + B.
- Follow the BIOS Recovery prompts if they appear.
3. Check Device Manager for Hidden Devices
- Open Device Manager.
- Select View > Show hidden devices.
- Expand Cameras, Imaging Devices, and Universal Serial Bus Controllers.
- Look for any unknown devices or devices with warning symbols.
I'm an HP Employee.
If this reply helped resolve your issue, please select the Accept as Solution as it helps others in the community quickly find the answer they’re looking for.
And if you found this reply helpful, clicking Yes below is a great way to let us know we’re providing the support you need, as it encourages us to keep improving and sharing helpful guidance.
06-13-2026 10:56 AM
Staying with my true fashion and self ..rather better late than never I’ve been able to work with the recent recommendations that you have given previously . I think that and hope that you will find the findings interesting.
1. UEFI looking to me that there are 2 ways to run that particular service! I have it downloaded from the HP website and into desktop and can also access for the phone via my phone I’ve run this now several times and have watched ad the simple issues are the ones that have the complicated outcomes/ Being said, personally I’ve not had the best of luck! As
06-13-2026 02:42 PM
Hi @JT33040,
Thank you for the update and for taking the time to work through the recommendations. I appreciate you sharing your findings.
From your description, it sounds like you've spent quite a bit of time testing the UEFI-related options and have already tried multiple approaches without success. Sometimes the simplest issues can indeed lead to the most unexpected troubleshooting results.
Since you mentioned this is related to the camera issue and the behavior appears to have started after recent system changes, one thing we could try is restoring the PC to a point when the camera was working correctly.
System Restore does not affect your personal files, but it can revert system settings, drivers, and updates that may have contributed to the issue.
To perform a System Restore:
- In Windows, search for Create a restore point and open it.
- Click System Restore.
- Select a restore point from a date when the camera was functioning properly.
- Follow the prompts to complete the restore process.
- Once the PC restarts, test the camera again.
If a suitable restore point is available, this can be a quick way to determine whether the issue is software-related.
Please let us know if you're able to perform the restore and whether the camera behavior changes afterwards. We'll be happy to continue working with you based on the results.
I'm an HP Employee.
If this reply helped resolve your issue, please select the Accept as Solution as it helps others in the community quickly find the answer they’re looking for.
And if you found this reply helpful, clicking Yes below is a great way to let us know we’re providing the support you need, as it encourages us to keep improving and sharing helpful guidance.
06-15-2026 07:41 PM
Wonderful.. I did see the replyp and I apologize on my end for not updating you on th Bios "Refresh" and the findings in device manager after having run what it was that I did. As for the Bios Ref resh, I was unable to complete that, as it was asking for the USB restore flash.. it did provide a web address, however, I was unable to capture that being said.. Device mgr and the snooping and expanding that i was asked to do, I believe opened up, what I think could very well be the answers that I had been seeking AND hoping for! I will list to best ability......
1. Viewing hidden.. seems that it did allow for quite a bit to be exposed now.. for starters the USB Caution that i see did once again surface.. I updated the driver and did all the same things with that particular as in past..
2. Camera.. expanded and it does NOT indicate by name anything other than USB and it is good... if that usb is not pluged in or has been uninstalled then it does not list.. now as for all the other stuff... after a careful exam I have now noticed a lot of things if I can recall correctly were related to some type of intergraded device.. lots of Intel.. All in all
Ok.. back to the grind!
Still I have not been able to fix the problem.. my question now is about the system restore..
I am sure that I am missing some important part of the step but I am under the impression that I am able to pick a time, ie 3 months ago lets say,, but the system automaticlly uses todays date and time for that point of recovery I really hope that I am not making it worse by all this stuff.. i can say that I have learned a lot.. now... about this error code still in regards to USB... please advise..
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 6/15/2026 6:22:40 PM
Event ID: 442
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: JTUpdated
Description:
Device settings for USB\VID_0000&PID_0001\5&1c89cdc0&0&16 were not migrated from previous OS installation due to partial or ambiguous device match.
Last Device Instance ID: USB\VID_0000&PID_0002\5&1c89cdc0&0&10
Class GUID: {36fc9e60-c465-11cf-8056-444553540000}
Location Path:
Migration Rank: 0xF000FFFFFFFFF100
Present: false
Status: 0xC0000719
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9c205a39-1250-487d-abd7-e831c6290539}" />
<EventID>442</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2026-06-15T23:22:40.6387778Z" />
<EventRecordID>876</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8756" />
<Channel>Microsoft-Windows-Kernel-PnP/Configuration</Channel>
<Computer>JTUpdated</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="DeviceInstanceId">USB\VID_0000&PID_0001\5&1c89cdc0&0&16</Data>
<Data Name="LastDeviceInstanceId">USB\VID_0000&PID_0002\5&1c89cdc0&0&10</Data>
<Data Name="ClassGuid">{36fc9e60-c465-11cf-8056-444553540000}</Data>
<Data Name="LocationPath">
</Data>
<Data Name="MigrationRank">0xf000fffffffff100</Data>
<Data Name="Present">false</Data>
<Data Name="Status">0xc0000719</Data>
</EventData>
</Event>
This is the most current for that particular one..
IDEA HERE??
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 6/15/2026 8:21:21 PM
Event ID: 10016
Task Category: None
Level: Warning
Keywords: Classic
User: JTUPDATED\mrnic
Computer: JTUpdated
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user JTUPDATED\mrnic SID (S-1-5-21-1242562818-42922134-457070475-1003) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="0">10016</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2026-06-16T01:21:21.1667309Z" />
<EventRecordID>9350</EventRecordID>
<Correlation ActivityID="{b61e959c-fd2c-0001-bd11-27b62cfddc01}" />
<Execution ProcessID="1328" ThreadID="8560" />
<Channel>System</Channel>
<Computer>JTUpdated</Computer>
<Security UserID="S-1-5-21-1242562818-42922134-457070475-1003" />
</System>
<EventData>
<Data Name="param1">application-specific</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Activation</Data>
<Data Name="param4">{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}</Data>
<Data Name="param5">{15C20B67-12E7-4BB6-92BB-7AFF07997402}</Data>
<Data Name="param6">JTUPDATED</Data>
<Data Name="param7">mrnic</Data>
<Data Name="param8">S-1-5-21-1242562818-42922134-457070475-1003</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
<Data Name="param10">Unavailable</Data>
<Data Name="param11">Unavailable</Data>
</EventData>
</Event>
This i belive i was able to fix had to do with me installing wrong driver for Intel Graphic... any way.. we are probably making a mountain out of a mole hill or at least I am.. hope this helps and I shall look forward to any more suggestions.. id like to stick with the core fix if possible as this has kind of become my baby lol
Quick note I did remove some of the boards and cables from the underside that were no longer needed and were inoperable. There is no change from when they were there just sitting, fyi. One of them though is the USB, it sat on the left side where the original DISK DRIVE was located. I do not know if that has anything to do with the issues. this was inop now for some time so I decided to just take it out. Thanks
06-17-2026 01:21 PM
Hi @JT33040,
Thank you for the detailed update and for taking the time to share your findings.
It’s great to hear that the investigation in Device Manager helped uncover some of the information you were looking for and that you were able to identify and address the Intel graphics driver issue. From what you've described, it sounds like you've made significant progress and have a much better understanding of the system's behavior.
The USB migration warning (Event ID 442) and the DCOM 10016 warning are commonly seen after hardware changes, Windows updates, driver changes, or device removals. Since you mentioned that the system behavior has not changed after removing the unused hardware and that the primary issue appears to be resolved, these entries may simply be remnants of previous hardware configurations rather than indications of an active fault.
We appreciate you sharing the additional details about the removed USB board and cables as well. Based on your observations, it does not appear that their removal introduced any new issues.
Most importantly, we're glad to know that the main concern has been resolved and that you've learned quite a bit through the process.
If you need any assistance in the future, whether it's related to this system or anything else HP-related, please don't hesitate to reach out. We'll be happy to help.
Take care, and thank you for keeping us updated.
I'm an HP Employee.
If this reply helped resolve your issue, please select the Accept as Solution as it helps others in the community quickly find the answer they’re looking for.
And if you found this reply helpful, clicking Yes below is a great way to let us know we’re providing the support you need, as it encourages us to keep improving and sharing helpful guidance.