By Ricardo Mitchell, M.Sc., B.Sc. – Crodymi LLC
What I expected to be a relatively straightforward Hyundai Event Data Recorder (EDR) retrieval turned into several hours of troubleshooting involving the vehicle, the Hyundai/GIT VCI interface, Windows drivers, security policies, technical support, and eventually the computer's BIOS/UEFI settings.
The assignment took place at Copart in Buffalo, New York. Fortunately, I arrived early. At the time, I did not realize how important that decision would become. What should have been a routine setup and EDR retrieval ended up consuming most of the time I had available at the facility.
The Copart staff were welcoming, cooperative, and helpful throughout the process. That made a significant difference because I needed considerably more time with the vehicle than I initially expected.
The First Sign That Something Was Wrong
After gaining access to the Hyundai and beginning the normal setup process, I connected the Hyundai/GIT equipment. Almost immediately, something did not look right.
The VCI was not showing the normal green light I expected to see.
Without that indication, I initially had to consider several possibilities. The vehicle's diagnostic connector could have lost power, a fuse could have been damaged, collision damage could have affected communication, a cable could have failed, the Windows computer could have had a problem, or the Hyundai/GIT interface itself could have failed.
At that point there was no obvious answer. All I knew was that the equipment I needed to complete the EDR retrieval was not communicating as expected.
Why the Situation Was Concerning
This was not an inexpensive consumer scan tool that could simply be replaced at a nearby store. The Hyundai/GIT equipment is specialized automotive diagnostic and forensic hardware. When the expected green light did not appear, the possibility that the interface itself had failed was a serious concern.
I had also traveled to the vehicle specifically to perform the EDR retrieval. A failed interface could mean an unsuccessful inspection, additional delays for the client, and potentially replacing an expensive piece of equipment.
Instead of immediately assuming the VCI was defective, I began working through the problem systematically.
Initial Symptoms
- The Hyundai/GIT VCI was not showing its expected green operating indication.
- The Hyundai EDR system would not establish the required communication.
- The GIT interface was not operating normally when connected.
- Windows was not properly recognizing and loading the VCI driver.
- Repeated reconnection attempts did not initially correct the problem.
What initially looked like a possible hardware failure eventually turned out to be much more complicated.
Get started
Start the process today — no upfront payment required. We’ll provide the service now, and you can settle the payment later.
Tell us what you need
Get updates & continue
Drop your email so we can follow up. You can skip if you prefer.
Hyundai Support Initially Suggested the VCI Might Be Dead
Because the normal green light was not appearing, I contacted Hyundai support while I was still at Copart.
During my first support contact, one of the possibilities presented to me was that the VCI itself might be dead. The absence of the green light appeared to support that possibility.
That was obviously not what I wanted to hear.
The equipment involved is expensive, specialized hardware, and at that moment I genuinely had to consider the possibility that I had lost an important piece of equipment. More importantly, if I accepted that conclusion immediately, the EDR retrieval would have ended there.
I decided not to give up.
I Needed to Prove Where the Failure Was Occurring
Before concluding that the Hyundai/GIT interface was defective, I wanted to determine whether the problem was actually coming from the vehicle.
I started working through the system one component at a time.
- I checked the vehicle-side connection.
- I checked the applicable fuse and power supply.
- I verified that power was available at the diagnostic connector.
- I tested the vehicle using other diagnostic equipment.
- I continued checking the computer and USB connection.
Testing with other equipment became an important part of the diagnosis. If another diagnostic interface could operate through the same vehicle DLC, then the Hyundai's diagnostic connector was not simply dead.
That meant I needed to look more closely at what was happening between Windows and the Hyundai/GIT VCI.
The Computer Became the Primary Suspect
I disconnected and reconnected the equipment several times. I restarted components, checked the USB connection, reviewed the software installation, and continued trying to determine why the GIT interface was not initializing.
I also worked through the security side of the computer. Norton was disabled during troubleshooting, Windows Security settings were examined, and the Hyundai/GIT software and driver package were reinstalled multiple times.
At first, none of those steps produced the result I needed.
The VCI still appeared to be unavailable, and the green light that I expected to see was still not giving me confidence that the interface was functioning.
This was the point where Device Manager became extremely important.
Windows Device Manager Revealed the Real Direction of the Problem
When I examined the Hyundai/GIT interface in Windows Device Manager, I discovered something much more useful than simply seeing that the VCI was not working.
Windows was detecting the device, but it was not properly loading the required driver.
The important error was:
Windows Device Manager Code 39
The driver involved in my case was:
HIVCUSB.sysThat changed my thinking considerably.
If Windows could detect the hardware but could not load its driver, then the VCI might not actually be dead. The problem could be the relationship between Windows, the Hyundai/GIT driver, and Windows security controls.
Checking Windows Code Integrity
I then began investigating whether Windows itself was blocking the Hyundai/GIT driver.
From an Administrator PowerShell window, I used the following command to examine recent Windows Code Integrity Event ID 3077 entries:
Get-WinEvent -FilterHashtable @{LogName='Microsoft-Windows-CodeIntegrity/Operational';Id=3077} -MaxEvents 5 | Format-List TimeCreated,MessageThe Code Integrity information helped identify that Windows security controls were involved in preventing the driver from loading normally.
In my case, the investigation identified an App Control / Code Integrity policy with the following GUID:
{8F9CB695-5D48-48D6-A329-7202B44607E3}Attempting to Remove the Policy
Once I identified the policy involved on my computer, I attempted to remove it using Microsoft's CiTool utility.
CiTool.exe --remove-policy "{8F9CB695-5D48-48D6-A329-7202B44607E3}"This is where the process became frustrating.
Running the command did not immediately solve the problem. I tried the policy-removal process several times, restarted the computer, returned to Device Manager, rechecked the VCI, and continued testing.
The Code 39 problem persisted.
Reinstalling the GIT Driver
I also continued reinstalling the Hyundai/GIT driver and running the driver installation components with Administrator privileges.
The process included disconnecting the VCI, reinstalling the driver package, restarting Windows, reconnecting the VCI, and checking Device Manager again before attempting another vehicle connection.
Instead of treating each failed attempt as proof that the hardware was dead, I kept using each result to narrow the problem.
Eventually, it became apparent that removing the Windows policy from within the normal Windows environment was not enough by itself.
The Policy Would Not Go Away Easily
One of the most difficult parts of the troubleshooting process was dealing with the Windows security policy that appeared to be preventing the Hyundai/GIT driver from loading.
I tried removing the policy several times. I restarted Windows, checked Device Manager, reran the commands, reinstalled the GIT driver, and continued testing the interface.
The problem would not simply disappear.
At that point, I had already spent a substantial amount of time at Copart. This is where arriving early really saved the assignment. Had I arrived later in the day, I may not have had enough time to continue working through the problem.
I Eventually Had to Reboot Into BIOS/UEFI
After the repeated Windows-side attempts failed to produce a lasting result, I eventually rebooted the computer and entered its BIOS/UEFI environment so I could address the security and boot configuration that was preventing the policy change from taking effect properly.
After making the necessary change, I returned to Windows and continued the policy-removal and driver troubleshooting process.
For the advanced portion of the troubleshooting, I also mounted the EFI System Partition using:
mountvol S: /sThe Windows Code Integrity policy files were located under the EFI Microsoft boot structure.
For the policy identified on my computer, the relevant path was:
S:\EFI\Microsoft\Boot\CiPolicies\Active\The policy file associated with the GUID I had identified could then be addressed directly:
Remove-Item "S:\EFI\Microsoft\Boot\CiPolicies\Active\{8F9CB695-5D48-48D6-A329-7202B44607E3}.cip" -ForceThen I Went Back Through the Driver Process Again
After dealing with the policy and restarting the computer, I returned to the Hyundai/GIT driver installation.
- I restarted Windows.
- I opened Device Manager.
- I checked the Hyundai/GIT VCI again.
- I reinstalled the required GIT driver where necessary.
- I ran the driver installation components with Administrator privileges.
- I reconnected the VCI.
- I allowed Windows to detect and initialize the interface.
- I checked Device Manager again before returning to the Hyundai EDR software.
The Troubleshooting Path
Connect Hyundai/GIT VCI
↓
No normal green light
↓
Hyundai support suggests possible dead VCI
↓
Check vehicle DLC and power
↓
Check fuse
↓
Test vehicle with other diagnostic equipment
↓
Vehicle-side connection appears functional
↓
Inspect Windows Device Manager
↓
Code 39 discovered
↓
HIVCUSB.sys identified
↓
Reinstall GIT software and driver
↓
Check Norton / Windows Security
↓
Review Code Integrity Event ID 3077
↓
Identify blocking policy
↓
Attempt policy removal
↓
Restart and retest
↓
Code 39 persists
↓
Repeat policy-removal attempts
↓
Reboot into BIOS/UEFI
↓
Address security / boot configuration
↓
Return to Windows
↓
Mount EFI System Partition
↓
Address active CI policy
↓
Restart Windows
↓
Reinstall / reload GIT driver
↓
VCI recognized correctly
↓
Return to Hyundai EDR softwareBy this point, the troubleshooting had moved far beyond simply checking a cable or reinstalling an application. The issue involved the way Windows was allowing the specialized Hyundai/GIT USB driver to load.
Get started
Start the process today — no upfront payment required. We’ll provide the service now, and you can settle the payment later.
Tell us what you need
Get updates & continue
Drop your email so we can follow up. You can skip if you prefer.
The Green Light Returned
Eventually, after working through the Windows driver problem, Code Integrity policy, repeated restarts, BIOS/UEFI changes, driver installation, and additional testing, the behavior of the Hyundai/GIT interface changed.
The VCI was recognized correctly and the operating indication I had been waiting for returned.
The green light was back.
That was an important moment because several hours earlier I had been faced with the possibility that the interface itself was dead.
It wasn't.
The Hyundai EDR Download Was Successfully Completed
Once Windows properly recognized the VCI and the GIT driver was operating, I returned to the Hyundai EDR software and attempted communication with the vehicle again.
This time the system communicated properly.
I was able to proceed with the Hyundai EDR retrieval and successfully complete the download at Copart.
Arriving Early Ultimately Saved the Day
One of the simplest lessons from this experience had nothing to do with computers.
Arriving early mattered.
I had expected the EDR retrieval itself to be the primary task. Instead, I spent most of my available time troubleshooting a problem that initially appeared to be failed hardware.
Because I arrived at Copart early, I had enough time to continue investigating instead of abandoning the assignment after the first few unsuccessful attempts.
The Copart staff were also welcoming and helpful throughout the process. Their cooperation gave me the opportunity to continue working with the vehicle while I tried to resolve the computer and VCI problem.
I Am Glad I Did Not Give Up on the Hardware
When I first contacted Hyundai support and was told that the absence of the green light could mean the VCI was dead, replacing the interface seemed like a real possibility.
Considering the cost and specialized nature of the equipment, that was concerning.
However, the troubleshooting evidence did not completely support giving up on the VCI. The vehicle DLC could be tested, Windows could see portions of the hardware, and Device Manager was providing a specific driver-related error.
Those clues were enough for me to continue.
The eventual successful EDR download confirmed that the interface itself had not been the fundamental problem.
What I Learned From the Experience
The most important lesson was to separate a vehicle communication problem from a computer-to-interface communication problem.
A Hyundai/GIT VCI that does not illuminate or communicate normally may certainly have a hardware problem, but that should not automatically be the conclusion.
When troubleshooting a similar situation, I would work through the problem in approximately this order:
- Check the vehicle DLC for power and ground.
- Check the appropriate vehicle fuses.
- Test the DLC with another diagnostic device.
- Inspect the USB connection and cables.
- Check Windows Device Manager.
- Record any Device Manager error code.
- Identify the affected driver.
- Reinstall the Hyundai/GIT VCI driver as Administrator.
- Review Windows Code Integrity events if the driver remains blocked.
- Investigate the specific Windows security policy identified on that computer.
- Restart and recheck Device Manager after each significant change.
- Verify that Windows recognizes the VCI correctly before returning to the vehicle.
Commands Used During My Troubleshooting
Review recent Windows Code Integrity Event ID 3077 entries:
Get-WinEvent -FilterHashtable @{LogName='Microsoft-Windows-CodeIntegrity/Operational';Id=3077} -MaxEvents 5 | Format-List TimeCreated,MessageRemove the Code Integrity policy identified on my computer:
CiTool.exe --remove-policy "{8F9CB695-5D48-48D6-A329-7202B44607E3}"Mount the EFI System Partition:
mountvol S: /sAddress the policy file identified during my troubleshooting:
Remove-Item "S:\EFI\Microsoft\Boot\CiPolicies\Active\{8F9CB695-5D48-48D6-A329-7202B44607E3}.cip" -ForceFinal Thoughts
This experience began with a Hyundai/GIT VCI showing no normal green indication and a reasonable concern that an expensive piece of hardware had failed.
It ended with a successful EDR download.
Between those two points were vehicle checks, calls for technical support, multiple software and driver reinstalls, Norton and Windows Security troubleshooting, Device Manager Code 39, the HIVCUSB.sys driver, Windows Code Integrity events, repeated attempts to remove a security policy, a BIOS/UEFI reboot, additional policy work, and a considerable amount of persistence.
For me, the experience reinforced a basic principle of technical troubleshooting: do not stop at the first plausible explanation. Follow the evidence until you can identify where the failure is actually occurring.
Crodymi LLC
EDR / Black Box Data Retrieval, EDR Analysis and Crash Reconstruction
Frequently Asked Questions
Hyundai EDR, GIT VCI, Windows Code 39, driver and vehicle communication troubleshooting.
1. Why is my Hyundai/GIT EDR VCI not connecting to the vehicle?
The problem may be on either the vehicle side or the computer side. First verify that the vehicle DLC has power and works with another diagnostic device.
If another scanner works through the same DLC but the Hyundai/GIT VCI does not, the problem may be associated with the VCI, USB connection, Windows driver, or Windows security configuration rather than the vehicle.
2. What does Windows Device Manager Code 39 mean with the Hyundai VCI?
Code 39 generally means Windows can identify the device but cannot properly load the required driver.
During my Hyundai/GIT troubleshooting, the affected driver was identified as:
HIVCUSB.sysThis was an important clue because it suggested that the VCI itself might not be dead. Windows was detecting the hardware but preventing its driver from operating correctly.
3. How can I determine whether the vehicle DLC is the problem?
Start with the vehicle before changing anything on the computer.
- Check DLC power.
- Verify the DLC grounds.
- Inspect the applicable vehicle fuses.
- Connect another compatible diagnostic scanner.
- Determine whether the second device powers up and communicates normally.
If another diagnostic interface operates through the same DLC, that significantly changes the direction of the troubleshooting. Attention can then shift toward the Hyundai/GIT VCI and computer.
4. What should I check in Windows Device Manager?
Locate the Hyundai/GIT VCI or associated USB device in Windows Device Manager and check for a yellow warning symbol.
Open the device properties and review:
- Device Status.
- The Windows error code.
- The driver name.
- Driver provider and version.
- Whether Windows reports that the driver could not be loaded.
In my case, Device Manager reported Code 39 and the investigation led to HIVCUSB.sys.
5. How do I check whether Windows Code Integrity is blocking the Hyundai driver?
Open PowerShell with Administrator privileges and review recent Windows Code Integrity Event ID 3077 entries.
Get-WinEvent -FilterHashtable @{LogName='Microsoft-Windows-CodeIntegrity/Operational';Id=3077} -MaxEvents 5 | Format-List TimeCreated,MessageThese events may help identify the executable, driver, or application-control policy responsible for preventing the Hyundai/GIT driver from loading.
6. Should I remove the same Windows policy GUID shown in this article?
No. A policy GUID identifies a particular policy. The GUID encountered on one computer should not automatically be assumed to be responsible for a problem on another computer.
First determine which policy is actually associated with the driver block on the computer being diagnosed.
7. Should I reinstall the Hyundai/GIT VCI driver?
Yes, especially when Device Manager is reporting a driver-related error.
- Disconnect the VCI.
- Reinstall the appropriate Hyundai/GIT driver package.
- Run the driver installer, such as
DrvInst.exe, with Administrator privileges. - Restart Windows.
- Reconnect the VCI.
- Return to Device Manager.
- Verify that the driver loads without an error.
- Then attempt the EDR connection again.
A successful software installation does not necessarily mean Windows successfully loaded the USB driver.
8. Can antivirus software or Windows Security prevent the Hyundai VCI from connecting?
Yes. Antivirus software, Windows application-control policies, driver-signing requirements, and Code Integrity protections can interfere with specialized or older automotive interface drivers.
During my troubleshooting, Norton and Windows security controls were among the areas investigated while determining why the Hyundai/GIT driver would not load.
The presence of a security product does not automatically mean it is responsible, so Device Manager and the Windows event logs should be used to establish what Windows is actually blocking.
9. Why does the Hyundai EDR software still fail after I reinstall it?
Reinstalling the Hyundai application and reinstalling the VCI driver are not necessarily the same thing.
The application can install successfully while Windows continues blocking or failing to load the USB driver required to communicate with the VCI.
After reinstalling the software, return to Device Manager and verify that the VCI is actually recognized and operating without a Windows error before attempting another EDR download.
10. What troubleshooting order should I follow when a Hyundai EDR connection fails?
- Verify vehicle DLC power and ground.
- Check the applicable vehicle fuses.
- Test the DLC using another compatible scanner.
- Inspect the USB cable and VCI connection.
- Open Windows Device Manager.
- Record any Windows error codes.
- Identify the affected VCI driver.
- Reinstall the appropriate Hyundai/GIT driver as Administrator.
- Restart Windows and recheck Device Manager.
- Review Windows Code Integrity Event ID 3077 if the driver remains blocked.
- Identify any applicable driver or security-policy conflict.
- Confirm that Windows recognizes the VCI correctly.
- Reconnect to the vehicle.
- Attempt the Hyundai EDR retrieval again.
Get started
Start the process today — no upfront payment required. We’ll provide the service now, and you can settle the payment later.
Tell us what you need
Get updates & continue
Drop your email so we can follow up. You can skip if you prefer.