Hi All,

What exactly should be done to initialize southbridge ICH6-M in AHCI mode? (I suppose that's what BIOS does every time before handing control over to OS)

Many thanks in advance!

I am using 7700K this time.

The main board is Asrock Fatality Gaming K6

The OS is Windows 10 Home.

But in Device Manager, there is an exclamation point.

So if you look

"KabyLake PCI Express Root Port # 10 - A2b1" This is the message."

So if you look at properties

"The device does not work properly because Windows can not load the required driver (code 31).

The specified request is an invalid operation on the target device. "

I get this message.

How does this exclamation disappear?

Is there no problem without using this?

I've reinstalled Windows several times to fix this.

But it did not work out.

I want you to solve it.

Thanks for reading.

I recently Installed brand new parts, and ran into some problems and fixed that just to boot up my computer and install all my drivers and The first one is my chipset driver... But when i do it through the CD i got for msi motherboards it just stops at 99%... Well my next plan is to install it thorugh your guys website and even at that it says unknown error can not install. And i get this crash report as follows:

[123C:12BC][2017-02-14T23:09:28]i001: Burn v3.10.0.1519, Windows v10.0 (Build 14393: Service Pack 0), path: C:\Users\Jacob\Downloads\Chipset_10.1.1.42_Public\10.1.1.42\SetupChipset.exe, cmdline: '-burn.unelevated BurnPipe.{FC14747E-D3E5-4DE7-934C-CD1717A1EDC0} {73E299B3-94DC-43DE-B7AC-50A478A56935} 1628 -overall'

[123C:12BC][2017-02-14T23:09:28]i000: Initializing string variable 'CHIPSET_PRODUCT_VERSION' to value '10.1.1.42'

[123C:12BC][2017-02-14T23:09:28]i000: Initializing string variable 'INSTALLER_BUILD_VERSION' to value '3.1'

[123C:12BC][2017-02-14T23:09:28]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx86.msi' to value ';NullDrivers.cab;NOT VersionNT64'

[123C:12BC][2017-02-14T23:09:28]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx64.msi' to value ';NullDrivers.cab;VersionNT64'

[123C:12BC][2017-02-14T23:09:29]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\Jacob\AppData\Local\Temp\Intel\Logs\Chipset_20170214230929.log'

[123C:12BC][2017-02-14T23:09:29]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\Jacob\Downloads\Chipset_10.1.1.42_Public\10.1.1.42\SetupChipset.exe'

[123C:12BC][2017-02-14T23:09:29]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Users\Jacob\Downloads\Chipset_10.1.1.42_Public\10.1.1.42\'

[123C:12BC][2017-02-14T23:09:29]i052: Condition 'VersionNT >= v6.1 OR (VersionNT = v6.0 AND NTProductType = 3)' evaluates to true.

[123C:12BC][2017-02-14T23:09:29]i000: Setting string variable 'WixBundleName' to value 'Intel(R) Chipset Device Software'

[123C:12BC][2017-02-14T23:09:29]i000: Loading managed bootstrapper application.

[123C:12BC][2017-02-14T23:09:29]i000: Creating BA thread to run asynchronously.

[123C:0B30][2017-02-14T23:09:29]i000: ** MBA ** Command line:-overall

[123C:0B30][2017-02-14T23:09:29]i000: Setting string variable 'WixBundleName' to value 'Intel(R) Chipset Device Software'

[123C:0B30][2017-02-14T23:09:29]i000: ** MBA ** Calling Engine.Detect()

[123C:12BC][2017-02-14T23:09:29]i100: Detect begin, 3 packages

[123C:12BC][2017-02-14T23:09:29]i000: Setting string variable 'DotNet35' to value '1'

[123C:12BC][2017-02-14T23:09:29]i000: Setting string variable 'DotNet40Client' to value '1'

[123C:12BC][2017-02-14T23:09:29]i000: Setting string variable 'DotNet40Full' to value '1'

[123C:12BC][2017-02-14T23:09:29]i000: Setting string variable 'DotNet45' to value '394802'

[123C:12BC][2017-02-14T23:09:29]i102: Detected related bundle: {c7f54569-0018-439c-809a-48046a4d4ebc}, type: Upgrade, scope: PerMachine, version: 10.1.1.9, operation: MajorUpgrade

[123C:12BC][2017-02-14T23:09:29]i000: ** MBA ** Related bundle detected: BundleTag: '' ProductCode: '{c7f54569-0018-439c-809a-48046a4d4ebc}' Version: '10.1.1.9' PerMachine: 'True' RelationType: 'Upgrade' Operation: 'MajorUpgrade' Result: 'None'

[123C:12BC][2017-02-14T23:09:29]i052: Condition 'DotNet35 OR DotNet40Client OR DotNet40Full OR (DotNet45 >= 378389)' evaluates to true.

[123C:12BC][2017-02-14T23:09:29]i101: Detected package: DotNet45, state: Present, cached: None

[123C:12BC][2017-02-14T23:09:29]i101: Detected package: SetupChipsetx86.msi, state: Absent, cached: None

[123C:12BC][2017-02-14T23:09:29]i104: Detected package: SetupChipsetx86.msi, feature: NullDriverFeature, state: Absent

[123C:12BC][2017-02-14T23:09:29]i104: Detected package: SetupChipsetx86.msi, feature: PackageVersionFeature, state: Absent

[123C:12BC][2017-02-14T23:09:29]i104: Detected package: SetupChipsetx86.msi, feature: LicenseAgreementFeature, state: Absent

[123C:12BC][2017-02-14T23:09:29]i101: Detected package: SetupChipsetx64.msi, state: Absent, cached: None

[123C:12BC][2017-02-14T23:09:29]i104: Detected package: SetupChipsetx64.msi, feature: NullDriverFeature, state: Absent

[123C:12BC][2017-02-14T23:09:29]i104: Detected package: SetupChipsetx64.msi, feature: PackageVersionFeature, state: Absent

[123C:12BC][2017-02-14T23:09:29]i104: Detected package: SetupChipsetx64.msi, feature: LicenseAgreementFeature, state: Absent

[123C:12BC][2017-02-14T23:09:29]i199: Detect complete, result: 0x0

[123C:12BC][2017-02-14T23:10:06]i200: Plan begin, 3 packages, action: Install

[123C:12BC][2017-02-14T23:10:06]w321: Skipping dependency registration on package with no dependency providers: DotNet45

[123C:12BC][2017-02-14T23:10:06]i052: Condition 'NOT VersionNT64' evaluates to false.

[123C:12BC][2017-02-14T23:10:06]i204: Plan 3 msi features for package: SetupChipsetx86.msi

[123C:12BC][2017-02-14T23:10:06]i203: Planned feature: NullDriverFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[123C:12BC][2017-02-14T23:10:06]i203: Planned feature: PackageVersionFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[123C:12BC][2017-02-14T23:10:06]i203: Planned feature: LicenseAgreementFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[123C:12BC][2017-02-14T23:10:06]i052: Condition 'VersionNT64' evaluates to true.

[123C:12BC][2017-02-14T23:10:06]i204: Plan 3 msi features for package: SetupChipsetx64.msi

[123C:12BC][2017-02-14T23:10:06]i203: Planned feature: NullDriverFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[123C:12BC][2017-02-14T23:10:06]i203: Planned feature: PackageVersionFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[123C:12BC][2017-02-14T23:10:06]i203: Planned feature: LicenseAgreementFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[123C:12BC][2017-02-14T23:10:06]i000: Setting string variable 'WixBundleRollbackLog_SetupChipsetx64.msi' to value 'C:\Users\Jacob\AppData\Local\Temp\Intel\Logs\Chipset_20170214230929_000_SetupChipsetx64.msi_rollback.log'

[123C:12BC][2017-02-14T23:10:06]i000: Setting string variable 'WixBundleLog_SetupChipsetx64.msi' to value 'C:\Users\Jacob\AppData\Local\Temp\Intel\Logs\Chipset_20170214230929_000_SetupChipsetx64.msi.log'

[123C:12BC][2017-02-14T23:10:06]i201: Planned package: DotNet45, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None

[123C:12BC][2017-02-14T23:10:06]i201: Planned package: SetupChipsetx86.msi, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None

[123C:12BC][2017-02-14T23:10:06]i201: Planned package: SetupChipsetx64.msi, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register

[123C:12BC][2017-02-14T23:10:06]i207: Planned related bundle: {c7f54569-0018-439c-809a-48046a4d4ebc}, type: Upgrade, default requested: Absent, ba requested: Absent, execute: Uninstall, rollback: Install, dependency: None

[123C:12BC][2017-02-14T23:10:06]i299: Plan complete, result: 0x0

[123C:0B30][2017-02-14T23:10:06]i000: Setting string variable 'IIF_MSI_SWITCHES' to value 'overall'

[123C:0B30][2017-02-14T23:10:06]i000: ** MBA ** Getting window handle.

[123C:0B30][2017-02-14T23:10:06]i000: ** MBA ** Calling Engine.Apply(). Window handle: 263614

[123C:12BC][2017-02-14T23:10:06]i300: Apply begin

[065C:06EC][2017-02-14T23:10:06]i370: Session begin, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{49bc1e38-39b4-4728-9e75-cbe67ba9a329}, options: 0x7, disable resume: No

[065C:06EC][2017-02-14T23:10:06]i000: Caching bundle from: 'C:\Users\Jacob\AppData\Local\Temp\{49bc1e38-39b4-4728-9e75-cbe67ba9a329}\.be\SetupChipset.exe' to: 'C:\ProgramData\Package Cache\{49bc1e38-39b4-4728-9e75-cbe67ba9a329}\SetupChipset.exe'

[065C:06EC][2017-02-14T23:10:06]i320: Registering bundle dependency provider: {49bc1e38-39b4-4728-9e75-cbe67ba9a329}, version: 10.1.1.42

[065C:06EC][2017-02-14T23:10:06]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{49bc1e38-39b4-4728-9e75-cbe67ba9a329}, resume: Active, restart initiated: No, disable resume: No

[065C:0C44][2017-02-14T23:10:06]i305: Verified acquired payload: SetupChipsetx64.msi at path: C:\ProgramData\Package Cache\.unverified\SetupChipsetx64.msi, moving to: C:\ProgramData\Package Cache\{36A16AC6-68D4-44C3-B224-608601D6B353}v10.1.1.42\SetupChipsetx64.msi.

[065C:0C44][2017-02-14T23:10:06]i305: Verified acquired payload: cab4FADBDD6DC6637E75E196F741A3F14D1 at path: C:\ProgramData\Package Cache\.unverified\cab4FADBDD6DC6637E75E196F741A3F14D1, moving to: C:\ProgramData\Package Cache\{36A16AC6-68D4-44C3-B224-608601D6B353}v10.1.1.42\media1.cab.

[065C:06EC][2017-02-14T23:10:06]i323: Registering package dependency provider: {36A16AC6-68D4-44C3-B224-608601D6B353}, version: 10.1.1.42, package: SetupChipsetx64.msi

[065C:06EC][2017-02-14T23:10:06]i301: Applying execute package: SetupChipsetx64.msi, action: Install, path: C:\ProgramData\Package Cache\{36A16AC6-68D4-44C3-B224-608601D6B353}v10.1.1.42\SetupChipsetx64.msi, arguments: ' MSIFASTINSTALL="7" IIF_MSI_SWITCHES="overall" ARPSYSTEMCOMPONENT="1"'

[065C:06EC][2017-02-14T23:10:09]e000: Error 0x80070652: Failed to install MSI package.

[065C:06EC][2017-02-14T23:10:09]e000: Error 0x80070652: Failed to execute MSI package.

[123C:12BC][2017-02-14T23:10:09]e000: Error 0x80070652: Failed to configure per-machine MSI package.

[123C:12BC][2017-02-14T23:10:09]i319: Applied execute package: SetupChipsetx64.msi, result: 0x80070652, restart: None

[123C:12BC][2017-02-14T23:10:09]e000: Error 0x80070652: Failed to execute MSI package.

[065C:06EC][2017-02-14T23:10:09]i318: Skipped rollback of package: SetupChipsetx64.msi, action: Uninstall, already: Absent

[123C:12BC][2017-02-14T23:10:09]i319: Applied rollback package: SetupChipsetx64.msi, result: 0x0, restart: None

[065C:06EC][2017-02-14T23:10:09]i329: Removed package dependency provider: {36A16AC6-68D4-44C3-B224-608601D6B353}, package: SetupChipsetx64.msi

[065C:06EC][2017-02-14T23:10:09]i351: Removing cached package: SetupChipsetx64.msi, from path: C:\ProgramData\Package Cache\{36A16AC6-68D4-44C3-B224-608601D6B353}v10.1.1.42\

[065C:06EC][2017-02-14T23:10:09]i329: Removed package dependency provider: {1B02E5E5-D964-4018-9CB0-9836B78BB375}, package: SetupChipsetx86.msi

[065C:06EC][2017-02-14T23:10:09]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{49bc1e38-39b4-4728-9e75-cbe67ba9a329}, resume: None, restart: None, disable resume: No

[065C:06EC][2017-02-14T23:10:09]i330: Removed bundle dependency provider: {49bc1e38-39b4-4728-9e75-cbe67ba9a329}

[065C:06EC][2017-02-14T23:10:09]i352: Removing cached bundle: {49bc1e38-39b4-4728-9e75-cbe67ba9a329}, from path: C:\ProgramData\Package Cache\{49bc1e38-39b4-4728-9e75-cbe67ba9a329}\

[065C:06EC][2017-02-14T23:10:09]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{49bc1e38-39b4-4728-9e75-cbe67ba9a329}, resume: None, restart initiated: No, disable resume: No

[123C:12BC][2017-02-14T23:10:09]i000: ** MBA ** Apply complete. Status: '-2147023278' Restart: 'None' Result: 'None'

[123C:12BC][2017-02-14T23:10:09]i399: Apply complete, result: 0x80070652, restart: None, ba requested restart:  No

[123C:0B30][2017-02-14T23:10:09]e000: ** MBA ** Unknown error.

[123C:0B30][2017-02-14T23:10:12]i000: ** MBA ** ResultCode=1618

[123C:12BC][2017-02-14T23:10:12]i500: Shutting down, exit code: 0x652

[123C:12BC][2017-02-14T23:10:12]i410: Variable: CHIPSET_PRODUCT_VERSION = 10.1.1.42

[123C:12BC][2017-02-14T23:10:12]i410: Variable: DotNet35 = 1

[123C:12BC][2017-02-14T23:10:12]i410: Variable: DotNet40Client = 1

[123C:12BC][2017-02-14T23:10:12]i410: Variable: DotNet40Full = 1

[123C:12BC][2017-02-14T23:10:12]i410: Variable: DotNet45 = 394802

[123C:12BC][2017-02-14T23:10:12]i410: Variable: IIF_ExtractionMapping_SetupChipsetx64.msi = ;NullDrivers.cab;VersionNT64

[123C:12BC][2017-02-14T23:10:12]i410: Variable: IIF_ExtractionMapping_SetupChipsetx86.msi = ;NullDrivers.cab;NOT VersionNT64

[123C:12BC][2017-02-14T23:10:12]i410: Variable: IIF_MSI_SWITCHES = overall

[123C:12BC][2017-02-14T23:10:12]i410: Variable: INSTALLER_BUILD_VERSION = 3.1

[123C:12BC][2017-02-14T23:10:12]i410: Variable: NTProductType = 1

[123C:12BC][2017-02-14T23:10:12]i410: Variable: VersionNT = 10.0.0.0

[123C:12BC][2017-02-14T23:10:12]i410: Variable: VersionNT64 = 10.0.0.0

[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleAction = 4

[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleElevated = 1

[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleLog = C:\Users\Jacob\AppData\Local\Temp\Intel\Logs\Chipset_20170214230929.log

[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleLog_SetupChipsetx64.msi = C:\Users\Jacob\AppData\Local\Temp\Intel\Logs\Chipset_20170214230929_000_SetupChipsetx64.msi.log

[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleManufacturer = Intel(R) Corporation

[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleName = Intel(R) Chipset Device Software

[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleOriginalSource = C:\Users\Jacob\Downloads\Chipset_10.1.1.42_Public\10.1.1.42\SetupChipset.exe

[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleOriginalSourceFolder = C:\Users\Jacob\Downloads\Chipset_10.1.1.42_Public\10.1.1.42\

[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleProviderKey = {49bc1e38-39b4-4728-9e75-cbe67ba9a329}

[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleRollbackLog_SetupChipsetx64.msi = C:\Users\Jacob\AppData\Local\Temp\Intel\Logs\Chipset_20170214230929_000_SetupChipsetx64.msi_rollback.log

[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleTag =

[123C:12BC][2017-02-14T23:10:12]i410: Variable: WixBundleVersion = 10.1.1.42

[123C:12BC][2017-02-14T23:10:12]i007: Exit code: 0x652, restarting: No

: Please help me out with this so i can make my computer run like its meant to run.

why aren't there any windows 10 drivers for this hardware ?

Hello guys and gal's why is this device only showing up with SIV ?

from this vendor SIV - System Information Viewer

the device don't show up before I used this software I didn't know it existed

after I restart the system its not there but showing as not present but as soon as I lunch siv its installed

saying no recourses are allocated because this device has a problem ?

info

Intel(R) 9 Series Chipset Family Thermal Controller - 8CA4

PCI\VEN_8086&DEV_8CA4&SUBSYS_85341043&REV_00\3&11583659&0&FE

PCI\VEN_8086&DEV_8CA4&SUBSYS_85341043&REV_00

PCI\VEN_8086&CC_118000

01802000

DN_DISABLEABLE

DN_NT_ENUMERATOR

DN_NT_DRIVER

{4d36e97d-e325-11ce-bfc1-08002be10318}

10.1.1.38

00FF2001

address : 001F0006

PCI Data Acquisition and Signal Processing Controller

driver key - {4d36e97d-e325-11ce-bfc1-08002be10318}\0059

PCI bus 0, device 31, function 6

PCIROOT(0)#PCI(1F06)

ACPI(_SB_)#ACPI(PCI0)#PCI(1F06)

\Device\NTPNP_PCI0014

01 00 04 90 00 00 00 00 00 00 00 00 00 00 00 00 14 00 00 00

02 00 5C 00 04 00 00 00 00 00 14 00 00 00 00 10 01 01 00 00

00 00 00 05 12 00 00 00 00 00 18 00 00 00 00 10 01 02 00 00

00 00 00 05 20 00 00 00 20 02 00 00 00 00 14 00 00 00 00 E0

01 01 00 00 00 00 00 01 00 00 00 00 00 00 14 00 00 00 00 A0

01 01 00 00 00 00 00 05 0C 00 00 00

I have just run the Intel Driver Update Utility, and it says that my Intel Chipset Device Software needs updating from version 10.0.14393.0 to version 10.1.1.14. But it also says, "See detailed description to make sure you need this file." How do I ascertain if I need this file/update?

I have tried the latest drivers for Windows10 / Windows7 and results from ping/throughput (iperf) test have been consistent since 18.40.0.0. After roaming through 3-5 access points, AIR-LAP1142N-A-K9  or AIR-CAP3702I-B-K9, clients don't continue to roam but temporarily disconnect then reconnect after 3-6sec sometimes longer. I have found that driver version 17.0.5.8 works flawless (acceptable <1-2sec network loss/roam) on 5.2xGhz using the AC-7260 Windows7 machine. Where can we get this driver to continue testing on the other three devices. Windows10 64-bit, AC-7265, AC-8260 and Windows7 AC-8260?

Food for thought: Devices have no issues roaming when adapter set to 2.4Ghz Preferred using latest drivers, 19.20 or 19.30. Due to hospital environment we need to have clinical device set to use only 5.2xGhz.

i tried to install driver for a printer and it says usb controller is in a failed state or not installed properly but i have no issues with anything usb that is plugged in. it all runs perfectly and when i go to device manager it shows my usb controller running properly. i have ran a usb troubleshooter and it says the controller is not working but yet everything works fine please help

Bonjour à tous.

j'ai acheté il y a 3 ans un ordinateur portable : Sleekbook HP Pavilion 15-b044sf.

celui-ci est équipé d'un chipset Intel High-Definition (HD).

Depuis quelques temps, je joue au jeu en ligne Slither.io

Mais avec ce PC (qui est le puis puissants de ceux que j'ai), pas moyen de jouer, ça saccade.

Or j'ai déjà formaté mon PC à plusieurs reprise en pensant que Windows était devenu lent.

Mais rien n'y fait.

Je suppose qu'il s'agit du drivers que j'utilise car il n'en existe pas pour Windows 10 (si je ne dis pas de bêtises ?)

Quelqu'un pourrait-il m'aider ?

Voici le numéro d'identification du matériel en question :

PCI\VEN_8086&DEV_0106&SUBSYS_1900103C&REV_09

Merci beaucoup pour votre aide.

Christophe

Hi there,

Here's me and another issue with my Windows 7 on my HP Pavilion 15-ab291sa.

The problem is that 8/10 times when I plug in my external HDD to any usb 3.0 ports the mouse will freeze for 5 seconds (I'm using wireless Logitech mouse with reciver pluged into one of the usb's).

I recently downgraded from Windows 10 to Windows 7 and I never had those problems under win10.

I have all the latest drivers for intel usb 3.0 controller installed.

I checked so many different solutions but nothing helped.

Any ideas, please?

Hello!

1. Does those Intel chipsets have AMT? Does they support KVM-VNC?

a) Intel G45 (Intel P45/P43 rev. A3 + Intel 82801JR (ICH10R) rev. 00)

b) Intel Z68 (Intel Sandy Bridge rev. 09 + Intel Z68 rev. B3)

c) Intel H170 (Intel Skylake rev. 07 + Intel Skylake PCH rev. 31)

2. Does Intel have list of all chipsets that provides preboot text console via KVM-VNC?

Hello!

It seems that Intel have some mans with brains so I hope you can help me a little...

I need to make one small server (based on standard but robust PC components Intel G45 + Q9550S) whole encrypted and with auto-reboot possibility without admin present each time. The purpose for encryption is to secure server data from direct access by unscrupulous datacenter stuff: by copying whole HDD, or just stealing 1 of 2 HDD from RAID, etc. And don't tell me about "case access alert" etc - this information will not help to protect stolen data.

What possibilities I already examine:

A) HDD password does not encrypt data at HDD, so if someone stole HDD its possible to open data by: removing password protection, change HDD controller to similar, etc.

B) Windows BitLocker with default settings have 2 huge security problems: a) all system is encrypts with keys that stored at unsecure area of the same HDD (yes, BL have many levels etc, but nevertheless its unsecure); b) data stored at user private area encrypts better and keys are hidden, but its impossible to access encrypted users data (like database or web server) without entering a password manually, so auto-reboot will not work. So at default settings BitLocker is useless.

C) TC/DC/BC/PGP/etc whole disk encryption have no security issue but they required a manually entered password at boot time - so admin must be there and enter password via keyboard.

D) PXE boot with DC have problem because DC loader with keys transfers via internet without encryption - it is a total security hole.

E) iPXE boot with DC already have TLS/HTTPS connection, but still require not encrypted boot image with DC keys that must always lie opened via internet and awaiting for server reboots - that is too a huge security problem because that host with boot-image can be broken by some hackers methods via internet.

F) iLO/RILOE/IP-KVM is a standalone old hardware versions of new Intel AMT-KVM technology and cost too high money for they primitive possibilities, also no one knows does they secure or not?!

G) Intel AMT with KVM-VNC gives possibility to enter password at boot time for whole disk encryption made by TC/DC/BC/PGP/etc via secure TLS/HTTPS protocol, but it still needs admin for password entering, so auto-reboot does not work.

H) So it seems that only automated and secure method is to use TPM soldered on MB (TPM added via TPM-connector also can be stolen or fastly copied). TPM can be used with BitLocker so encryption keys will lie inside soldered on motherboard TPM - that is secure enough (not many can crack TPM and extract keys from it).

So here is my questions:

1. Does anyone can add something to my list? Another methods? Problems resolves?

2. What method of server encryption do you use and recommend?

3. What method you can suggest to owners of motherboards without soldered TPM, without TPM-connectors, without Intel AMT-KVM? (as I have)

Hi,

I have to configure a RMM software on a couple of machines which have some Intel stuff on-board. I thought the easiest way would be to monitor the Windows Event logs, but I don't know in which event logs and under which source name the Intel stuff reports.

Some Examples:

* Intel Network Connections

* Intel Graphic Driver

* Intel Management Engine Components

* Intel Rapid Storage Technology

* Intel Security Assist

* Intel USB 3.0 Host Controller Adaptation Driver

* ...

I know not everything is important, and needs to be monitored. But for Example The Intel Rapid Storage Technology should be in charge of the harddisks, and it would be nice to know if there is a problem.

Thanks for any information/help,

Christian.

Hi

I need to have 2 serial ports with the E3800 chipset on a embedded system under Windows 10.

I installed the HSUART drivers from the Win10 Atom E3800 BSP and I still get only exclamation marks on the 2 UART.

I am also not able to have them initialized as legacy COM.

What do I have to do to be able to use these UART as RS232 ports?

Cheers,

McL

I am running a Z97 board.  Latest Intel RST drivers downloaded from Intel's website.

RAID0 is made of 3x 300GB 7200rpm mechanical drive

Cache is a 64GB Sandisk SSD

I am getting really bad performance with this setup.  looking at the Task Manager (Windows 10) the RAID0 volume is is getting 50% usage with Write about 30MB/sec.  About 30-45mins it will settle down, but the performance is still really bad.  read performance is never passes 80MB/sec and mostly around 45-60MB/sec.

Please help

hello,

i have an issue installing intel management engine. first, when i uninstalled the older version the pc froze and i had to hard reset it. after restarting the uninstallation could not complete anymore with a fatal error. i cleaned / removed the remaining installation, entries and such as good as i could. now, i am unable to install it again with a fatal error again.

logs attached.

is there a way to fix this?

Here are my specs:

Processor: Core i5 6400

Motherboard: ASRock H110M-ITX (H110 chipset)

Operating system: Windows 7 Ultimate SP1 (64-bit)

USB driver: Intel USB 3.0 xHCI driver (5.0.0.32)

I managed to install Windows 7 and the USB 3.0 drivers, but there are a few issues.

1) If I plug certain 2.0 devices (such as thumb drives) on a 3.0 port, Windows can't install the drivers. If I plug them on a 2.0 port, the drivers are installed and now I can plug them on 3.0 ports without issues.

2) I can't install the drivers for an HP printer because the setup can't detect any USB controller and cancels installation. If I run Microsoft USB Fix It (https://support.microsoft.com/en-us/help/17614/automatically-diagnose-and-fix-windows-usb-problems), it says "The USB Controller is in a failed state or is not currently installed". USBView (https://msdn.microsoft.com/en-us/library/windows/hardware/ff560019(v=vs.85).aspx) recognizes all ports and connected devices.

Experimenting with USB Legacy and other UEFI options didn't help.

Hi there,

I have got an issue with a custom USB 2.0 device (with our own firmware) regarding enumeration and driver installation in windows 7 using USB 3.0 extensible Host Controller driver.

The devices uses the BOS descriptor (OS 1.0) to provide a compatible ID (RNDIS) for selecting the appropriate inf file / driver (rndiscmp.inf / rndiscmp6.sys). This works fine in Windows 7 using (native Microsoft) USB 2.0 driver and also in Windows 8 using USB 3.0 or 2.0 with MS driver (on many different installations). But it does not work in Windows 7 using intel USB 3.0 extensible Host Controller (using a VIA Chipset/driver stack it works!). Analyzing USB traffic I can observe that the Descriptor is requested from the device. Hereupon the compatible ID is sent to the PC but it can not be found in registry and hence it is not used to select the driver automatically (evaluating setupapi.dev). The driver must be chosen manually then.

Actually the USB requests are the same as in the USB 2.0 case but something goes wrong in intel USB 3.0 driver stack.

Does anybody have any idea? Or any additional debugging possibility?

Thank you very much!

Martin

In order to upgrade our system I have developed a Windows PE 5.0(Windows 8.1's Preinstallation Environment) image/USB drive that can boot our system and copy a Windows Embedded Standard 7 image onto our target hardware platform.  However, our system has a cabling/noise defect that is causing a USB 3.0 thumbdrive to perform extremely slow on file transfers from the USB drive to an internal CFast drive.  I have found that if I use a USB 2.0 extension cable the drive performs much faster.  Fixing the hardware for the field is not an option, it is becoming difficult to find USB 2.0 drives as most companies are obsoleting these drives, and we would prefer not to ship a short USB 2 extension cable with each USB 3.0 drive.

I have found a SuperUser question, windows 7 - Force a single USB 3.0 port to work as USB 2.0 - Super User, that is very similar to my problem and has gotten me half way to a software workaround.  In it a user has described using a setpci utility to configure the USB controller to use USB 2.0 speeds.  However, this command causes Windows PE to no longer see the already connected USB drive.  If I physically disconnect and reconnect the drive after the setpci commands then Windows PE sees the drive again and it is able to transfer the files at reasonable speeds.  I'm looking for a way in software to trigger the rediscovery of the USB drive.  I have been unsuccessful in using devcon to get Windows to detect the drive or rescan the USB Hub 3.0 without a restart.

Are there some additional setpci calls that would directly cause the Intel Chipset Series 7 PCH to rescan/restart the USB Hub 3.0 and relay to Windows the drive is connected?  I'm a Windows developer so I'm having difficulty understanding the information in the datasheet that describes a USB Command register that does have a reset port bit, but I'm not sure how to use setpci to interact with these registers or if this USB Command reset would do what I'm looking for.

Thanks,

Dave

Hello.

I installed Chipset Driver 10.1.1.42, but install is failed.

I heard that the installation was successful, but the installation was not actually done. Also, SMBus driver and some other has been showing "No driver is installed for this device."

I also forced the installation using the -overall option, but the driver's date was marked 1/1/1970 and the same thing happened.

After that, I could not solve the symptom even if I forced downgrading or deleting the driver. Also, when I tried to install a lower version of the driver in such a state, I got an unconditional downgrade warning.

The new driver is causing me a lot of trouble. I do not want to reinstall Windows because of this problem. Please help me.