Windows 10: USB-USBHUB3 Event 196

Getting this on freshly installed laptopUSB device draining system power when system is idle. USB Device: VID: 0x8087 PID: 0x29 REV: 0x1 Removal action failed: SkippedAsRecentIoObserveredThis causes quite a high battery drain during sleepI initially thought it was BT/Wifi card,

:)

 

Installing windows off of a USB stick

Step By Step from vista:
From admin cmd prompt

1. diskpart
1a. list disk
2. select disk 1 (replace 1 with your usb drive)
3. clean
4. create partition primary
5. select partition 1 (replace 1 with your usb drive)
6. active
7. format fs=fat32
8. assign
9. exit

Copy Windows Vista's DVD ROM content to the Flash Drive

xcopy d:\*.* /s/e/f e:\ (d being your vista cd and e being your usb stick)

And that's it, boot off your usb disk

 

USB Device (USB Stick) Not Recognised by Windows 10

Here is some info from the dump files:

BUGCODE_USB3_DRIVER (144)

This bugcheck usually happens when the USB3 core stack detects an invalid

operation being performed by a USB client. This bugcheck may also occur

due to hardware failure on a USB Boot Device.

Arguments:

Arg1: 0000000000003003, USB3_WER_BUGCODE_USBHUB3_DEVICE_ENUMERATION_FAILURE

A USB device failed enumeration.

Arg2: ffffd701b324d838, USBHUB3_LIVEDUMP_CONTEXT

Arg3: 0000000040010011, 0

Arg4: 0000000000000000, 0

BugCheck 144, {3003, ffffd701b324d838, 40010011, 0}

Probably caused by : UsbHub3.sys ( UsbHub3!TelemetryData_CreateReport+ba )

The issue appears to be with the UsbHub3.sys which is a component of Windows.

As the UsbHub3.sys appears to be at version 10.0.14393.0 I am going to suggest to try installing the Creators Update which will update the UsbHub3.sys and perhaps correct any configuration issue.

As a general precaution back up any critical files beforehand. Consider uninstalling Kaspersky beforehand (use Windows Defender and firewall instead) and then you could reinstall Kaspersky afterwards.

Also, does the USB stick work if plugged into a USB 2.0 port?

 

Export All Administrative Events to Excel

To analyze events, from the Windows Event Viewer, there is a simple way to export all Administrative Events to Excel, with PowerShell.

Exporting all Administrative Events to Excel is a simple two Step process, as described here:

Step 1 - Create the Administrative Events View .xml file

1. Open Eventviewer (%windir%\system32\eventvwr.msc)
2. Navigate to: Event Viewer (Local) > Custom Views > Administrative Events
3. In the “Actions” pane select “Filter Current Custom View”.
4. Select the the XML tab.
5. Press Ctrl+A to select all the XML code of the Custom View.
6. Open a notepad, paste the selected code and save the file to your Desktop as AdmEvtView.xml

Step 2 - Create the csv file with the events

1. Download the ExportEvtCSV.zip file, which contains the script ExportEvtCSV.ps1 and unzip it, on your Desktop.
   It's not a fancy script, just basic PowerShell commands to create a csv file on the Desktop.
2. In Windows Search, type “ISE” (without the quotes) to open “Windows PowerShell ISE” and Run as administrator
   
3. To allow running the script, change the ExecutionPolicy, for this session. To do that, in the Console pane type:
   Code:
4. In the Windows PowerShell ISE, open and run the script: ExportEvtCSV.ps1
   The script will create a csv file with a name YYYYMMDD.HHMM.csv on the Desktop
5. When done, open the newly created .csv file, format the columns as needed and optionally save it as .xlsx, if you wish.

That’s it! You now have all the Administrative Events in Excel for filtering and further analysis.

Now to the more technical hard stuff... *Confused

There is a reason for running the script from within PowerShell ISE!

It would be great if everything was also working perfectly, when running the script from an elevated PowerShell too.

We can run it from an elevated PowerShell, which means that you just follow the Step 1, as above but for the Step 2 instead of the ISE you run the script from an elevated PowerShell.

The problem is that it will work only for anybody who has en-US format for the dates. Everyone else, who has another format (i.e. en-GB, fr-FR, el-GR etc.), the dates are not translated properly by Excel (although the script uses the –UseCulture switch) and remain as text in the en-US format.

I'm not sure if this a bug of the "export-csv" cmdlet, but although it runs the way it supposed to from within the ISE, from PowerShell there is a problem with the dates format.
As I haven’t found a way to overcome this obstacle, any suggestion from the PowerShell gurus of the forum (like my good friend Shawn @Brink, for instance), is welcome.