For several years I have been happily running a 3-disk RAID5 using Intel Matrix Storage Manager on my office Dell Precision T3500 under Windows 7-64 bit. In May the Microsoft upgrade tool migrated it to Windows 10 (unprompted), and a few weeks later I noticed that the Intel matrix storage console was no longer available, so I can no longer monitor the status of individual disks other than via the BIOS Ctrl-I facility. I can't roll back to Windows 7 because Microsoft has deleted the windows.old data (which I now understand happens after a month).

Last week a disk failure occurred (array degraded notice during startup, slow computer, Error ocurred message by one of the disks), so I have replaced one of the 3 hard drives (WD black 1TB), expecting it to be rebuilt into the array as occurs under Windows 7. This doesn't seem to happen, despite a successful message when the new disk is recognised saying the disk will now be rebuilt in the operating system.

What actually happens is a BSOD immediately after the drive change (I have had two BSODs so far, UNEXPECTED_STORE_EXCEPTION and KERNEL_DATA_INPAGE_ERROR). After an error report/reboot all appears fine but the drive never gets rebuilt and on subsequent reboots shows up as an Unknown Disk in the BIOS utility.

Device manager reports my RAID controller (Intel(R) ICH8R/ICH9R/ICH10R/DO/PCH SATA RAID Controller) is on version 8.9.2.1002 from August 2009. I am unsure whether newer versions (I see it is now called Intel RST) will be compatible with my hardware and am nervous to try in case I end up with a brick. I can't find any advice from Intel. Dell won't help because it's an old system. Microsoft, whose fault this is, said they would get back to me within 2 days but their latest response doesn't fill me with confidence ("Sure, I will look for all the possible solution to get this issue fix and I will email it to you once I found any good solution.").

So my immediate question is:

How can I get my replacement disk recognised and rebuilt into the array?

Hello and thank you ahead of time for any assistance,

     In an attempt to install the latest version of the Intel drivers on my computer, I came across the Intel Driver Update Utility.  Each time I attempt to install the utility, I get a fatal error and cannot figure out what the problem is.

Here is the log file:

[2718:2248][2016-10-05T11:03:02]i001: Burn v3.10.3.3007, Windows v10.0 (Build 14393: Service Pack 0), path: C:\Users\tpolk\AppData\Local\Temp\{88A6BD96-3458-47F5-98FB-C02CC8CFD06F}\.cr\Intel Driver Update Utility Installer.exe

[2718:2248][2016-10-05T11:03:02]i000: Initializing string variable 'LaunchTarget' to value '[ProgramFilesFolder]\Intel Driver Update Utility\DriverUpdateUI.exe'

[2718:2248][2016-10-05T11:03:02]i009: Command Line: '"-burn.clean.room=D:\tpolk\Downloads\Intel Driver Update Utility Installer.exe" -burn.filehandle.attached=828 -burn.filehandle.self=64'

[2718:2248][2016-10-05T11:03:02]i000: Setting string variable 'WixBundleOriginalSource' to value 'D:\tpolk\Downloads\Intel Driver Update Utility Installer.exe'

[2718:2248][2016-10-05T11:03:02]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'D:\tpolk\Downloads\'

[2718:2248][2016-10-05T11:03:02]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\tpolk\AppData\Local\Temp\Intel®_Driver_Update_Utility_20161005110302.log'

[2718:2248][2016-10-05T11:03:02]i000: Setting string variable 'WixBundleName' to value 'Intel® Driver Update Utility'

[2718:2248][2016-10-05T11:03:02]i000: Setting string variable 'WixBundleManufacturer' to value 'Intel'

[2718:2530][2016-10-05T11:03:02]i000: Setting numeric variable 'WixStdBALanguageId' to value 1033

[2718:2530][2016-10-05T11:03:02]i000: Setting version variable 'WixBundleFileVersion' to value '2.6.1.4'

[2718:2248][2016-10-05T11:03:02]i100: Detect begin, 4 packages

[2718:2248][2016-10-05T11:03:02]i000: Setting string variable 'NETFRAMEWORK45' to value '394802'

[2718:2248][2016-10-05T11:03:02]i052: Condition 'NETFRAMEWORK45 >= 378389' evaluates to true.

[2718:2248][2016-10-05T11:03:02]i101: Detected package: NetFx45Web, state: Present, cached: None

[2718:2248][2016-10-05T11:03:02]i101: Detected package: IPIPInstallerX64, state: Absent, cached: None

[2718:2248][2016-10-05T11:03:02]i101: Detected package: IPIPInstallerX86, state: Absent, cached: None

[2718:2248][2016-10-05T11:03:02]i101: Detected package: DriverUpdateUtilityInstaller, state: Absent, cached: None

[2718:2248][2016-10-05T11:03:02]i199: Detect complete, result: 0x0

[2718:2530][2016-10-05T11:03:07]i000: Setting numeric variable 'EulaAcceptCheckbox' to value 1

[2718:2248][2016-10-05T11:03:07]i200: Plan begin, 4 packages, action: Install

[2718:2248][2016-10-05T11:03:07]w321: Skipping dependency registration on package with no dependency providers: NetFx45Web

[2718:2248][2016-10-05T11:03:07]i052: Condition 'VersionNT64' evaluates to true.

[2718:2248][2016-10-05T11:03:07]i000: Setting string variable 'WixBundleRollbackLog_IPIPInstallerX64' to value 'C:\Users\tpolk\AppData\Local\Temp\Intel®_Driver_Update_Utility_20161005110302_000_IPIPInstallerX64_rollback.log'

[2718:2248][2016-10-05T11:03:07]i000: Setting string variable 'WixBundleLog_IPIPInstallerX64' to value 'C:\Users\tpolk\AppData\Local\Temp\Intel®_Driver_Update_Utility_20161005110302_000_IPIPInstallerX64.log'

[2718:2248][2016-10-05T11:03:07]i052: Condition 'NOT VersionNT64' evaluates to false.

[2718:2248][2016-10-05T11:03:07]i000: Setting string variable 'WixBundleRollbackLog_DriverUpdateUtilityInstaller' to value 'C:\Users\tpolk\AppData\Local\Temp\Intel®_Driver_Update_Utility_20161005110302_001_DriverUpdateUtilityInstaller_rollback.log'

[2718:2248][2016-10-05T11:03:07]i000: Setting string variable 'WixBundleLog_DriverUpdateUtilityInstaller' to value 'C:\Users\tpolk\AppData\Local\Temp\Intel®_Driver_Update_Utility_20161005110302_001_DriverUpdateUtilityInstaller.log'

[2718:2248][2016-10-05T11:03:07]i201: Planned package: NetFx45Web, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None

[2718:2248][2016-10-05T11:03:07]i201: Planned package: IPIPInstallerX64, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register

[2718:2248][2016-10-05T11:03:07]i201: Planned package: IPIPInstallerX86, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None

[2718:2248][2016-10-05T11:03:07]i201: Planned package: DriverUpdateUtilityInstaller, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register

[2718:2248][2016-10-05T11:03:07]i299: Plan complete, result: 0x0

[2718:2248][2016-10-05T11:03:07]i300: Apply begin

[2718:2248][2016-10-05T11:03:07]i010: Launching elevated engine process.

[2718:2248][2016-10-05T11:03:07]i011: Launched elevated engine process.

[2718:2248][2016-10-05T11:03:07]i012: Connected to elevated engine.

[1E58:2904][2016-10-05T11:03:07]i358: Pausing automatic updates.

[1E58:2904][2016-10-05T11:03:07]i359: Paused automatic updates.

[1E58:2904][2016-10-05T11:03:07]i360: Creating a system restore point.

[1E58:2904][2016-10-05T11:03:08]w363: Could not create system restore point, error: 0x80070422. Continuing...

[1E58:2904][2016-10-05T11:03:08]i370: Session begin, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{fe2eebd3-ee15-4538-bb19-b627e3f2a911}, options: 0x7, disable resume: No

[1E58:2904][2016-10-05T11:03:08]i000: Caching bundle from: 'C:\Users\tpolk\AppData\Local\Temp\{1D485CC5-392D-4B67-AF20-F49A8B7E1A52}\.be\Intel Driver Update Utility Installer.exe' to: 'C:\ProgramData\Package Cache\{fe2eebd3-ee15-4538-bb19-b627e3f2a911}\Intel Driver Update Utility Installer.exe'

[1E58:2904][2016-10-05T11:03:08]i320: Registering bundle dependency provider: {fe2eebd3-ee15-4538-bb19-b627e3f2a911}, version: 2.6.1.4

[1E58:2904][2016-10-05T11:03:08]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{fe2eebd3-ee15-4538-bb19-b627e3f2a911}, resume: Active, restart initiated: No, disable resume: No

[1E58:2630][2016-10-05T11:03:08]i305: Verified acquired payload: IPIPInstallerX64 at path: C:\ProgramData\Package Cache\.unverified\IPIPInstallerX64, moving to: C:\ProgramData\Package Cache\{DB52A2D0-CAA1-4ED1-B122-29E7EDDE187F}v2.1.28.3\IntelProductImprovementProgramInstaller.msi.

[1E58:2630][2016-10-05T11:03:08]i305: Verified acquired payload: DriverUpdateUtilityInstaller at path: C:\ProgramData\Package Cache\.unverified\DriverUpdateUtilityInstaller, moving to: C:\ProgramData\Package Cache\{06DA421D-EE23-487D-878F-F0AF97EF69AD}v2.6.1.4\Intel Driver Update Utility Installer.msi.

[1E58:2904][2016-10-05T11:03:08]i323: Registering package dependency provider: {DB52A2D0-CAA1-4ED1-B122-29E7EDDE187F}, version: 2.1.28.3, package: IPIPInstallerX64

[1E58:2904][2016-10-05T11:03:08]i301: Applying execute package: IPIPInstallerX64, action: Install, path: C:\ProgramData\Package Cache\{DB52A2D0-CAA1-4ED1-B122-29E7EDDE187F}v2.1.28.3\IntelProductImprovementProgramInstaller.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'

[2718:2248][2016-10-05T11:03:12]i319: Applied execute package: IPIPInstallerX64, result: 0x0, restart: None

[1E58:2904][2016-10-05T11:03:12]i325: Registering dependency: {fe2eebd3-ee15-4538-bb19-b627e3f2a911} on package provider: {DB52A2D0-CAA1-4ED1-B122-29E7EDDE187F}, package: IPIPInstallerX64

[1E58:2904][2016-10-05T11:03:12]i323: Registering package dependency provider: {06DA421D-EE23-487D-878F-F0AF97EF69AD}, version: 2.6.1.4, package: DriverUpdateUtilityInstaller

[1E58:2904][2016-10-05T11:03:12]i301: Applying execute package: DriverUpdateUtilityInstaller, action: Install, path: C:\ProgramData\Package Cache\{06DA421D-EE23-487D-878F-F0AF97EF69AD}v2.6.1.4\Intel Driver Update Utility Installer.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'

[1E58:2904][2016-10-05T11:03:39]e000: Error 0x80070643: Failed to install MSI package.

[1E58:2904][2016-10-05T11:03:39]e000: Error 0x80070643: Failed to execute MSI package.

[2718:2248][2016-10-05T11:03:39]e000: Error 0x80070643: Failed to configure per-machine MSI package.

[2718:2248][2016-10-05T11:03:39]i319: Applied execute package: DriverUpdateUtilityInstaller, result: 0x80070643, restart: None

[2718:2248][2016-10-05T11:03:39]e000: Error 0x80070643: Failed to execute MSI package.

[1E58:2904][2016-10-05T11:03:39]i318: Skipped rollback of package: DriverUpdateUtilityInstaller, action: Uninstall, already: Absent

[2718:2248][2016-10-05T11:03:39]i319: Applied rollback package: DriverUpdateUtilityInstaller, result: 0x0, restart: None

[1E58:2904][2016-10-05T11:03:39]i329: Removed package dependency provider: {06DA421D-EE23-487D-878F-F0AF97EF69AD}, package: DriverUpdateUtilityInstaller

[1E58:2904][2016-10-05T11:03:39]i351: Removing cached package: DriverUpdateUtilityInstaller, from path: C:\ProgramData\Package Cache\{06DA421D-EE23-487D-878F-F0AF97EF69AD}v2.6.1.4\

[1E58:2904][2016-10-05T11:03:39]i329: Removed package dependency provider: {679012E8-DFAC-4484-AD14-D08C6FD7FB4B}, package: IPIPInstallerX86

[1E58:2904][2016-10-05T11:03:39]i326: Removed dependency: {fe2eebd3-ee15-4538-bb19-b627e3f2a911} on package provider: {DB52A2D0-CAA1-4ED1-B122-29E7EDDE187F}, package IPIPInstallerX64

[1E58:2904][2016-10-05T11:03:39]i301: Applying rollback package: IPIPInstallerX64, action: Uninstall, path: (null), arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'

[2718:2248][2016-10-05T11:03:39]i319: Applied rollback package: IPIPInstallerX64, result: 0x0, restart: None

[1E58:2904][2016-10-05T11:03:39]i329: Removed package dependency provider: {DB52A2D0-CAA1-4ED1-B122-29E7EDDE187F}, package: IPIPInstallerX64

[1E58:2904][2016-10-05T11:03:39]i351: Removing cached package: IPIPInstallerX64, from path: C:\ProgramData\Package Cache\{DB52A2D0-CAA1-4ED1-B122-29E7EDDE187F}v2.1.28.3\

[1E58:2904][2016-10-05T11:03:39]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{fe2eebd3-ee15-4538-bb19-b627e3f2a911}, resume: None, restart: None, disable resume: No

[1E58:2904][2016-10-05T11:03:39]i330: Removed bundle dependency provider: {fe2eebd3-ee15-4538-bb19-b627e3f2a911}

[1E58:2904][2016-10-05T11:03:39]i352: Removing cached bundle: {fe2eebd3-ee15-4538-bb19-b627e3f2a911}, from path: C:\ProgramData\Package Cache\{fe2eebd3-ee15-4538-bb19-b627e3f2a911}\

[1E58:2904][2016-10-05T11:03:39]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{fe2eebd3-ee15-4538-bb19-b627e3f2a911}, resume: None, restart initiated: No, disable resume: No

[2718:2248][2016-10-05T11:03:40]i399: Apply complete, result: 0x80070643, restart: None, ba requested restart:  No

Does anyone have any ideas?  Thank you for reading.

Hey guys,

I am looking for a version of Mobile 5th Generation Intel(R) Core(TM) Camarillo Device - 1603 driver which can function Win 8.1.

Can you help me? It is for a Dell XPS13 9343. Thank you so much!

Sourcire

[18BC:07D4][2016-10-06T21:02:40]i001: Burn v3.7.1224.0, Windows v6.2 (Build 9200: Service Pack 0), path: C:\Users\Bryan\Downloads\Intel Components\SetupChipset.exe, cmdline: '-burn.unelevated BurnPipe.{0CE0F48D-1FC7-4B5F-B964-125C12A0C54C} {479B04F4-9810-4E16-91AA-D85AD43885EA} 204'

[18BC:07D4][2016-10-06T21:02:40]i000: Initializing string variable 'IIF_ProductVersion' to value '10.1.1.14'

[18BC:07D4][2016-10-06T21:02:40]i000: Initializing string variable 'IIF_InstallerVersion' to value '3.1.6'

[18BC:07D4][2016-10-06T21:02:40]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx86.msi' to value ';NullDrivers.cab;NOT VersionNT64'

[18BC:07D4][2016-10-06T21:02:40]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx64.msi' to value ';NullDrivers.cab;VersionNT64'

[18BC:07D4][2016-10-06T21:02:40]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\Bryan\AppData\Local\Temp\Intel\Logs\Chipset_20161006210240.log'

[18BC:07D4][2016-10-06T21:02:40]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\Bryan\Downloads\Intel Components\SetupChipset.exe'

[18BC:07D4][2016-10-06T21:02:40]i052: Condition 'VersionNT >= v6.1 OR (VersionNT = v6.0 AND NTProductType = 3)' evaluates to true.

[18BC:07D4][2016-10-06T21:02:40]i000: Setting string variable 'WixBundleName' to value 'Intel(R) Chipset Device Software'

[18BC:07D4][2016-10-06T21:02:40]i000: Loading managed bootstrapper application.

[18BC:07D4][2016-10-06T21:02:41]i000: Creating BA thread to run asynchronously.

[18BC:0C48][2016-10-06T21:02:41]i000: ** MBA ** Command line:

[18BC:0C48][2016-10-06T21:02:41]i000: Setting string variable 'WixBundleName' to value 'Intel(R) Chipset Device Software'

[18BC:0C48][2016-10-06T21:02:41]i000: ** MBA ** Calling Engine.Detect()

[18BC:07D4][2016-10-06T21:02:41]i100: Detect begin, 3 packages

[18BC:07D4][2016-10-06T21:02:41]i000: Setting string variable 'DotNet35' to value '1'

[18BC:07D4][2016-10-06T21:02:41]i000: Setting string variable 'DotNet40Client' to value '1'

[18BC:07D4][2016-10-06T21:02:41]i000: Setting string variable 'DotNet40Full' to value '1'

[18BC:07D4][2016-10-06T21:02:41]i000: Setting string variable 'DotNet45' to value '394802'

[18BC:07D4][2016-10-06T21:02:41]i052: Condition 'DotNet35 OR DotNet40Client OR DotNet40Full OR (DotNet45 >= 378389)' evaluates to true.

[18BC:07D4][2016-10-06T21:02:41]i103: Detected related package: {FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}, scope: PerMachine, version: 10.1.1.14, language: 0 operation: MajorUpgrade

[18BC:07D4][2016-10-06T21:02:41]i101: Detected package: DotNet45, state: Present, cached: None

[18BC:07D4][2016-10-06T21:02:41]i101: Detected package: SetupChipsetx86.msi, state: Absent, cached: None

[18BC:07D4][2016-10-06T21:02:41]i104: Detected package: SetupChipsetx86.msi, feature: NullDriverFeature, state: Absent

[18BC:07D4][2016-10-06T21:02:41]i104: Detected package: SetupChipsetx86.msi, feature: PackageVersionFeature, state: Absent

[18BC:07D4][2016-10-06T21:02:41]i104: Detected package: SetupChipsetx86.msi, feature: LicenseAgreementFeature, state: Absent

[18BC:07D4][2016-10-06T21:02:41]i101: Detected package: SetupChipsetx64.msi, state: Present, cached: None

[18BC:07D4][2016-10-06T21:02:41]i104: Detected package: SetupChipsetx64.msi, feature: NullDriverFeature, state: Local

[18BC:07D4][2016-10-06T21:02:41]i104: Detected package: SetupChipsetx64.msi, feature: PackageVersionFeature, state: Local

[18BC:07D4][2016-10-06T21:02:41]i104: Detected package: SetupChipsetx64.msi, feature: LicenseAgreementFeature, state: Local

[18BC:07D4][2016-10-06T21:02:41]i199: Detect complete, result: 0x0

[18BC:07D4][2016-10-06T21:02:49]i200: Plan begin, 3 packages, action: Install

[18BC:07D4][2016-10-06T21:02:49]w321: Skipping dependency registration on package with no dependency providers: DotNet45

[18BC:07D4][2016-10-06T21:02:49]i052: Condition 'NOT VersionNT64' evaluates to false.

[18BC:07D4][2016-10-06T21:02:49]i204: Plan 3 msi features for package: SetupChipsetx86.msi

[18BC:07D4][2016-10-06T21:02:49]i203: Planned feature: NullDriverFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[18BC:07D4][2016-10-06T21:02:49]i203: Planned feature: PackageVersionFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[18BC:07D4][2016-10-06T21:02:49]i203: Planned feature: LicenseAgreementFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[18BC:07D4][2016-10-06T21:02:49]i052: Condition 'VersionNT64' evaluates to true.

[18BC:07D4][2016-10-06T21:02:49]i000: ** MBA ** SetupChipsetx64.msi: Converting 'Install' to 'Repair'.

[18BC:07D4][2016-10-06T21:02:49]i204: Plan 3 msi features for package: SetupChipsetx64.msi

[18BC:07D4][2016-10-06T21:02:49]i203: Planned feature: NullDriverFeature, state: Local, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[18BC:07D4][2016-10-06T21:02:49]i203: Planned feature: PackageVersionFeature, state: Local, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[18BC:07D4][2016-10-06T21:02:49]i203: Planned feature: LicenseAgreementFeature, state: Local, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[18BC:07D4][2016-10-06T21:02:49]i000: Setting string variable 'WixBundleLog_SetupChipsetx64.msi' to value 'C:\Users\Bryan\AppData\Local\Temp\Intel\Logs\Chipset_20161006210240_0_SetupChipsetx64.msi.log'

[18BC:07D4][2016-10-06T21:02:49]i201: Planned package: DotNet45, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None

[18BC:07D4][2016-10-06T21:02:49]i201: Planned package: SetupChipsetx86.msi, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None

[18BC:07D4][2016-10-06T21:02:49]i201: Planned package: SetupChipsetx64.msi, state: Present, default requested: Present, ba requested: Repair, execute: Repair, rollback: None, cache: Yes, uncache: No, dependency: Register

[18BC:07D4][2016-10-06T21:02:49]i299: Plan complete, result: 0x0

[18BC:0C48][2016-10-06T21:02:49]i000: Setting string variable 'IIF_MSI_SWITCHES' to value ''

[18BC:0C48][2016-10-06T21:02:49]i000: ** MBA ** Getting window handle.

[18BC:0C48][2016-10-06T21:02:49]i000: ** MBA ** Calling Engine.Apply(). Window handle: 3212024

[18BC:07D4][2016-10-06T21:02:49]i300: Apply begin

[00CC:0850][2016-10-06T21:02:50]i000: Caching bundle from: 'C:\Users\Bryan\AppData\Local\Temp\{619e726e-d2b4-4e28-9568-c964fd81ee6c}\.be\SetupChipset.exe' to: 'C:\ProgramData\Package Cache\{619e726e-d2b4-4e28-9568-c964fd81ee6c}\SetupChipset.exe'

[00CC:0850][2016-10-06T21:02:50]i320: Registering bundle dependency provider: {619e726e-d2b4-4e28-9568-c964fd81ee6c}, version: 10.1.1.14

[00CC:1B60][2016-10-06T21:02:50]i305: Verified acquired payload: SetupChipsetx64.msi at path: C:\ProgramData\Package Cache\.unverified\SetupChipsetx64.msi, moving to: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\SetupChipsetx64.msi.

[00CC:1B60][2016-10-06T21:02:50]i305: Verified acquired payload: cab4FADBDD6DC6637E75E196F741A3F14D1 at path: C:\ProgramData\Package Cache\.unverified\cab4FADBDD6DC6637E75E196F741A3F14D1, moving to: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\media1.cab.

[00CC:0850][2016-10-06T21:02:50]i323: Registering package dependency provider: {FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}, version: 10.1.1.14, package: SetupChipsetx64.msi

[00CC:0850][2016-10-06T21:02:50]i301: Applying execute package: SetupChipsetx64.msi, action: Repair, path: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\SetupChipsetx64.msi, arguments: ' MSIFASTINSTALL="7" IIF_MSI_SWITCHES="" ARPSYSTEMCOMPONENT="1"'

[00CC:0850][2016-10-06T21:03:11]e000: Error 0x80070643: Failed to run maintanance mode for MSI package.

[00CC:0850][2016-10-06T21:03:11]e000: Error 0x80070643: Failed to execute MSI package.

[18BC:07D4][2016-10-06T21:03:11]e000: Error 0x80070643: Failed to configure per-machine MSI package.

[18BC:07D4][2016-10-06T21:03:11]i319: Applied execute package: SetupChipsetx64.msi, result: 0x80070643, restart: None

[18BC:07D4][2016-10-06T21:03:11]e000: Error 0x80070643: Failed to execute MSI package.

[00CC:0850][2016-10-06T21:03:11]i329: Removed package dependency provider: {FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}, package: SetupChipsetx64.msi

[00CC:0850][2016-10-06T21:03:11]i351: Removing cached package: SetupChipsetx64.msi, from path: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\

[00CC:0850][2016-10-06T21:03:11]i329: Removed package dependency provider: {23312E5E-F714-4F0B-97F5-4A7E2DEFE61E}, package: SetupChipsetx86.msi

[00CC:0850][2016-10-06T21:03:11]i330: Removed bundle dependency provider: {619e726e-d2b4-4e28-9568-c964fd81ee6c}

[00CC:0850][2016-10-06T21:03:11]i352: Removing cached bundle: {619e726e-d2b4-4e28-9568-c964fd81ee6c}, from path: C:\ProgramData\Package Cache\{619e726e-d2b4-4e28-9568-c964fd81ee6c}\

[18BC:07D4][2016-10-06T21:03:11]i000: ** MBA ** Apply complete. Status: '-2147023293' Restart: 'None' Result: 'None'

[18BC:07D4][2016-10-06T21:03:11]i399: Apply complete, result: 0x80070643, restart: None, ba requested restart:  No

[18BC:0C48][2016-10-06T21:03:11]e000: ** MBA ** Unknown error.

Hi,

I recently upgraded to Windows10 Pro 64bit and I noticed that the RST service is not running (icon has a yellow "!" mark) and my computer was slightly slower than before. I'm not very good in these stuff but I feel something's wrong when a driver is not working. I tried restarting the service manually, ran it in compatibility mode, and it all failed. I tried the Intel Update Utility but it did not detect any new drivers. I also tried to install the latest 14.5.0.1081 driver (SetupRST.exe) manually from Intel's download site but it showed a failure message and says "This platform is not supported"

I really need help with this, thanks!

I can't install Intel Extreme Tuning Utility on Windows 10 Anniverary because it says the kernel driver isn't signed.

https://tech.slashdot.org/story/16/07/31/2146234/all-windows-10-kernel-mode-drivers-must-be-digitally-signed-by-microsof…

In event viewer it says:

"The iocbios2 service failed to start due to the following error:

Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source."

Is there a newer version than 6.1.2.8 that fixes this?

Thanks

その2件の「ドライバー更新」をクリックしたのですが、エラーが発生しインストールが終了してしまいました。

その際に表示されたのは下記のものです。

Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C26

Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C2D

インテルのDriver Update Utility 2.6を試みたのですが、やはりエラーが発生し「失敗」と表示される状態です。

その際に検索されたのは「チップセット・デバイス・ソフトウェア（INF　アップデート・ユーティリティーEXE)」でした。

ログファイルは下記の通りとなります。

現在、コードレスマウスや、USBメモリーが使用できずに困っています。

WIN7が自動更新でWIN10になっています。@

解決策を教えてください。

よろしお願いいたします。

================quote=============

DriverUpdateUI.exe Error: 0 : System.Windows.Markup.XamlParseException: 指定されたバインディング制約に一致する型 'DriverUpdateUI.MainWindow' のコンストラクターの呼び出しで例外がスローされました。 ---> System.IO.IOException: 別のプロセスで使用されているため、プロセスはファイル 'C:\Users\hokka\AppData\Local\Temp\IntelDLM\debugFile.Log' にアクセスできません。

   場所 System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

   場所 System.IO.File.InternalDelete(String path, Boolean checkHost)

   場所 System.IO.File.Delete(String path)

   場所 DriverUpdateUI.MainWindow.PrepareLogFile()

   場所 DriverUpdateUI.MainWindow..ctor()

   --- 内部例外スタック トレースの終わり ---

   場所 System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)

   場所 System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)

   場所 System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)

   場所 System.Windows.Application.LoadBamlStreamWithSyncInfo(Stream stream, ParserContext pc)

   場所 System.Windows.Application.LoadComponent(Uri resourceLocator, Boolean bSkipJournaledProperties)

   場所 System.Windows.Application.DoStartup()

   場所 System.Windows.Application.<.ctor>b__1_0(Object unused)

   場所 System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)

   場所 System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

DriverUpdateUI.exe Error: 0 : System.Windows.Markup.XamlParseException: 指定されたバインディング制約に一致する型 'DriverUpdateUI.MainWindow' のコンストラクターの呼び出しで例外がスローされました。 ---> System.IO.IOException: 別のプロセスで使用されているため、プロセスはファイル 'C:\Users\hokka\AppData\Local\Temp\IntelDLM\debugFile.Log' にアクセスできません。

   場所 System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

   場所 System.IO.File.InternalDelete(String path, Boolean checkHost)

   場所 System.IO.File.Delete(String path)

   場所 DriverUpdateUI.MainWindow.PrepareLogFile()

   場所 DriverUpdateUI.MainWindow..ctor()

   --- 内部例外スタック トレースの終わり ---

   場所 System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)

   場所 System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)

   場所 System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)

   場所 System.Windows.Application.LoadBamlStreamWithSyncInfo(Stream stream, ParserContext pc)

   場所 System.Windows.Application.LoadComponent(Uri resourceLocator, Boolean bSkipJournaledProperties)

   場所 System.Windows.Application.DoStartup()

   場所 System.Windows.Application.<.ctor>b__1_0(Object unused)

   場所 System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)

   場所 System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

   場所 System.Windows.Threading.DispatcherOperation.InvokeImpl()

   場所 System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)

   場所 System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

   場所 System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

   場所 System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

   場所 MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)

   場所 System.Windows.Threading.DispatcherOperation.Invoke()

   場所 System.Windows.Threading.Dispatcher.ProcessQueue()

   場所 System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

   場所 MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

   場所 MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)

   場所 System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)

   場所 System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

   場所 System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)

   場所 MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)

   場所 MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)

   場所 System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)

   場所 System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)

   場所 System.Windows.Application.RunDispatcher(Object ignore)

   場所 System.Windows.Application.RunInternal(Window window)

   場所 System.Windows.Application.Run(Window window)

   場所 DriverUpdateUI.App.Main()

================unquote=============

Hi everyone

I pretend to port coreboot to a system that has the (Intel® DH82C222 PCH) Specifications  chipset.

The problem is that I was not able to find the fsp (firmware support package) for this chipset.

Does anyone know were I can find it?

Thanks and Regards

Rafael R. Nachado

I have an Alienware Area 51 R2 desktop, which uses the Intel X99 chipset. This appears to be Intel RST 14.

I wish to use three large drives in a RAID 5 configuration. This will be a data volume (no boot).

What limitations need to be considered in selecting a drive? Are there capacity or other restrictions? The only limit I've found so far are that older drivers require 512e, but I run Windows 10 and have fully up to date RST drivers.

Is there any reason three 10TB Seagate IronWolf NAS drives would not work in a RAID 5 configuration? This is Seagate model number ST10000VN0004

How can I get RAID alarms in my software? I have Intel Rapid Storage 14.8 on Windows 7; in previous version there was a Command Line Intarface, but I can't find it for this driver version, is there some API that I can use in my software?

HELP ME I CAN NOT USE THE USBS.I HAVE TO RESET WIN 10 AFTER THE RESET THERE WAS ONLY 1 USB WORKING AND TELL ME I NEED TO UPDATE TO THIS CHIP SET. BUT THE COMPUTER GIVE ME THIS ERROR.

I cannot set the cache mode to Write Through for my single desk drive

I have a 3 disk system:

1x  Samsung 850 Pro M2.SSD 512GB
2x  Western Digital Red 3TB

I created two drives

1. Containing only the Samsung 850 Pro, no RAID

2. Containing both WD's in RAID1

Intel Rapid Storage lists all of them in the Storage System View

The top is the WD RAID1 set and I can click both the set and the individual disks on port 0 and 1

The 2nd is the Samsung 850 Pro on port 7

I can change the Cache mode for my RAID 1 set but not for my SSD drive as shown below.

How do I change the Cache more for my single drive SSD?

I installed the new RST 14.0.0.1143 on my Z87 Mainboard with Windows 8.1 yesterday. Since there are no F6 drivers yet, i started the setup and then looked in %temp%, and there were the familiar x86 and x64 folders, just like in the F6 drivers. So i updated the driver from there via the device manager.

Something i soon noticed was wrong: The HDDs didn't spin down anymore after the 30 minutes i defined in the power savings plan.

At first i thought there could be something wrong with the extracted F6 driver files, but the folder content matched with the previous F6 drivers, and there was nothing unusual in the INF files either, which i compared. Just some new strings for newer chipsets.

I then made a roll-back to the old 13.6.0.1002 driver via device manager. The HDDs spun down after 30 minutes, everything normal.

To rule out that the 14.0.0.1143 drivers actually require the RST software to function properly, i installed the whole RST 14.0.0.1143. But with that, there is another problem, so i couldn't analyze the original problem further. The RST software keeps polling the SMART data from the HDDs and thus prevents them from spinning down anyway.

In Process Monitor, it looks like so:

1. 23:21:55,2169899IAStorDataMgrSvc.exe 4880CreateFile \Device\Harddisk0\DR0 SUCCESS DesiredAccess:GenericRead/Write,Disposition:Open,Options:Synchronous IO Non-Alert,Non-DirectoryFile,Attributes: n/a,ShareMode:Read,Write,AllocationSize: n/a,OpenResult:Opened
2. 23:21:55,2170929IAStorDataMgrSvc.exe 4880DeviceIoControl \Device\Harddisk0\DR0 SUCCESS Control: SMART_RCV_DRIVE_DATA
3. 23:21:55,2172062IAStorDataMgrSvc.exe 4880DeviceIoControl \Device\Harddisk0\DR0 SUCCESS Control: IOCTL_SCSI_PASS_THROUGH_DIRECT
4. 23:21:55,2175240IAStorDataMgrSvc.exe 4880CloseFile \Device\Harddisk0\DR0 SUCCESS
5. 23:21:55,2196952IAStorDataMgrSvc.exe 4880CreateFile \Device\Harddisk1\DR1 SUCCESS DesiredAccess:GenericRead/Write,Disposition:Open,Options:Synchronous IO Non-Alert,Non-DirectoryFile,Attributes: n/a,ShareMode:Read,Write,AllocationSize: n/a,OpenResult:Opened
6. 23:21:55,2197896IAStorDataMgrSvc.exe 4880DeviceIoControl \Device\Harddisk1\DR1 SUCCESS Control: SMART_RCV_DRIVE_DATA
7. 23:21:55,2198977IAStorDataMgrSvc.exe 4880CloseFile \Device\Harddisk1\DR1 SUCCESS
8. 23:21:55,2220264IAStorDataMgrSvc.exe 4880CreateFile \Device\Harddisk2\DR2 SUCCESS DesiredAccess:GenericRead/Write,Disposition:Open,Options:Synchronous IO Non-Alert,Non-DirectoryFile,Attributes: n/a,ShareMode:Read,Write,AllocationSize: n/a,OpenResult:Opened
9. 23:21:55,2221176IAStorDataMgrSvc.exe 4880DeviceIoControl \Device\Harddisk2\DR2 SUCCESS Control: SMART_RCV_DRIVE_DATA
10. 23:21:55,2222212IAStorDataMgrSvc.exe 4880CloseFile \Device\Harddisk2\DR2 SUCCESS
11. 23:21:55,2244052IAStorDataMgrSvc.exe 4880CreateFile \Device\Harddisk3\DR3 SUCCESS DesiredAccess:GenericRead/Write,Disposition:Open,Options:Synchronous IO Non-Alert,Non-DirectoryFile,Attributes: n/a,ShareMode:Read,Write,AllocationSize: n/a,OpenResult:Opened
12. 23:21:55,2244945IAStorDataMgrSvc.exe 4880DeviceIoControl \Device\Harddisk3\DR3 SUCCESS Control: SMART_RCV_DRIVE_DATA
13. 23:21:55,2245982IAStorDataMgrSvc.exe 4880CloseFile \Device\Harddisk3\DR3 SUCCESS

So i uninstalled RST and went back to the 14.0 F6 drivers only for analyzing. But no matter what i tried, even setting the spin-down to 1 minute in the power management, the HDDs won't spin down with the new driver.

I read a bit more about the mechanism here: http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/Disk_Idle_Detection.doc

Apparently the power manager, after the defined time, sends a request packet to the disk driver, asking for the HDD to go from D0 state (fully on) to D3 state (standby, stop spinning). Then the disk driver should convert this packet into an ATA command, telling the drive to enter standby. But from what i see, the drive never receives this command with the RST 14.0. When i roll back to 13.6.0.1002, it works fine again. With the 14.0, no go, i tried everything. And contrary to when you install the full RST software, with just the F6 driver there is also no SMART data polling that could interrupt things.

I'm at a loss here. Sadly i don't have the "PwrTest" tool from the Windows Driver Kit to test the mechanisms any further. But i'm hoping for someone else to know what's going on, or at least reproduce this possible bug.

[18BC:07D4][2016-10-06T21:02:40]i001: Burn v3.7.1224.0, Windows v6.2 (Build 9200: Service Pack 0), path: C:\Users\Bryan\Downloads\Intel Components\SetupChipset.exe, cmdline: '-burn.unelevated BurnPipe.{0CE0F48D-1FC7-4B5F-B964-125C12A0C54C} {479B04F4-9810-4E16-91AA-D85AD43885EA} 204'

[18BC:07D4][2016-10-06T21:02:40]i000: Initializing string variable 'IIF_ProductVersion' to value '10.1.1.14'

[18BC:07D4][2016-10-06T21:02:40]i000: Initializing string variable 'IIF_InstallerVersion' to value '3.1.6'

[18BC:07D4][2016-10-06T21:02:40]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx86.msi' to value ';NullDrivers.cab;NOT VersionNT64'

[18BC:07D4][2016-10-06T21:02:40]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx64.msi' to value ';NullDrivers.cab;VersionNT64'

[18BC:07D4][2016-10-06T21:02:40]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\Bryan\AppData\Local\Temp\Intel\Logs\Chipset_20161006210240.log'

[18BC:07D4][2016-10-06T21:02:40]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\Bryan\Downloads\Intel Components\SetupChipset.exe'

[18BC:07D4][2016-10-06T21:02:40]i052: Condition 'VersionNT >= v6.1 OR (VersionNT = v6.0 AND NTProductType = 3)' evaluates to true.

[18BC:07D4][2016-10-06T21:02:40]i000: Setting string variable 'WixBundleName' to value 'Intel(R) Chipset Device Software'

[18BC:07D4][2016-10-06T21:02:40]i000: Loading managed bootstrapper application.

[18BC:07D4][2016-10-06T21:02:41]i000: Creating BA thread to run asynchronously.

[18BC:0C48][2016-10-06T21:02:41]i000: ** MBA ** Command line:

[18BC:0C48][2016-10-06T21:02:41]i000: Setting string variable 'WixBundleName' to value 'Intel(R) Chipset Device Software'

[18BC:0C48][2016-10-06T21:02:41]i000: ** MBA ** Calling Engine.Detect()

[18BC:07D4][2016-10-06T21:02:41]i100: Detect begin, 3 packages

[18BC:07D4][2016-10-06T21:02:41]i000: Setting string variable 'DotNet35' to value '1'

[18BC:07D4][2016-10-06T21:02:41]i000: Setting string variable 'DotNet40Client' to value '1'

[18BC:07D4][2016-10-06T21:02:41]i000: Setting string variable 'DotNet40Full' to value '1'

[18BC:07D4][2016-10-06T21:02:41]i000: Setting string variable 'DotNet45' to value '394802'

[18BC:07D4][2016-10-06T21:02:41]i052: Condition 'DotNet35 OR DotNet40Client OR DotNet40Full OR (DotNet45 >= 378389)' evaluates to true.

[18BC:07D4][2016-10-06T21:02:41]i103: Detected related package: {FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}, scope: PerMachine, version: 10.1.1.14, language: 0 operation: MajorUpgrade

[18BC:07D4][2016-10-06T21:02:41]i101: Detected package: DotNet45, state: Present, cached: None

[18BC:07D4][2016-10-06T21:02:41]i101: Detected package: SetupChipsetx86.msi, state: Absent, cached: None

[18BC:07D4][2016-10-06T21:02:41]i104: Detected package: SetupChipsetx86.msi, feature: NullDriverFeature, state: Absent

[18BC:07D4][2016-10-06T21:02:41]i104: Detected package: SetupChipsetx86.msi, feature: PackageVersionFeature, state: Absent

[18BC:07D4][2016-10-06T21:02:41]i104: Detected package: SetupChipsetx86.msi, feature: LicenseAgreementFeature, state: Absent

[18BC:07D4][2016-10-06T21:02:41]i101: Detected package: SetupChipsetx64.msi, state: Present, cached: None

[18BC:07D4][2016-10-06T21:02:41]i104: Detected package: SetupChipsetx64.msi, feature: NullDriverFeature, state: Local

[18BC:07D4][2016-10-06T21:02:41]i104: Detected package: SetupChipsetx64.msi, feature: PackageVersionFeature, state: Local

[18BC:07D4][2016-10-06T21:02:41]i104: Detected package: SetupChipsetx64.msi, feature: LicenseAgreementFeature, state: Local

[18BC:07D4][2016-10-06T21:02:41]i199: Detect complete, result: 0x0

[18BC:07D4][2016-10-06T21:02:49]i200: Plan begin, 3 packages, action: Install

[18BC:07D4][2016-10-06T21:02:49]w321: Skipping dependency registration on package with no dependency providers: DotNet45

[18BC:07D4][2016-10-06T21:02:49]i052: Condition 'NOT VersionNT64' evaluates to false.

[18BC:07D4][2016-10-06T21:02:49]i204: Plan 3 msi features for package: SetupChipsetx86.msi

[18BC:07D4][2016-10-06T21:02:49]i203: Planned feature: NullDriverFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[18BC:07D4][2016-10-06T21:02:49]i203: Planned feature: PackageVersionFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[18BC:07D4][2016-10-06T21:02:49]i203: Planned feature: LicenseAgreementFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[18BC:07D4][2016-10-06T21:02:49]i052: Condition 'VersionNT64' evaluates to true.

[18BC:07D4][2016-10-06T21:02:49]i000: ** MBA ** SetupChipsetx64.msi: Converting 'Install' to 'Repair'.

[18BC:07D4][2016-10-06T21:02:49]i204: Plan 3 msi features for package: SetupChipsetx64.msi

[18BC:07D4][2016-10-06T21:02:49]i203: Planned feature: NullDriverFeature, state: Local, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[18BC:07D4][2016-10-06T21:02:49]i203: Planned feature: PackageVersionFeature, state: Local, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[18BC:07D4][2016-10-06T21:02:49]i203: Planned feature: LicenseAgreementFeature, state: Local, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None

[18BC:07D4][2016-10-06T21:02:49]i000: Setting string variable 'WixBundleLog_SetupChipsetx64.msi' to value 'C:\Users\Bryan\AppData\Local\Temp\Intel\Logs\Chipset_20161006210240_0_SetupChipsetx64.msi.log'

[18BC:07D4][2016-10-06T21:02:49]i201: Planned package: DotNet45, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None

[18BC:07D4][2016-10-06T21:02:49]i201: Planned package: SetupChipsetx86.msi, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None

[18BC:07D4][2016-10-06T21:02:49]i201: Planned package: SetupChipsetx64.msi, state: Present, default requested: Present, ba requested: Repair, execute: Repair, rollback: None, cache: Yes, uncache: No, dependency: Register

[18BC:07D4][2016-10-06T21:02:49]i299: Plan complete, result: 0x0

[18BC:0C48][2016-10-06T21:02:49]i000: Setting string variable 'IIF_MSI_SWITCHES' to value ''

[18BC:0C48][2016-10-06T21:02:49]i000: ** MBA ** Getting window handle.

[18BC:0C48][2016-10-06T21:02:49]i000: ** MBA ** Calling Engine.Apply(). Window handle: 3212024

[18BC:07D4][2016-10-06T21:02:49]i300: Apply begin

[00CC:0850][2016-10-06T21:02:50]i000: Caching bundle from: 'C:\Users\Bryan\AppData\Local\Temp\{619e726e-d2b4-4e28-9568-c964fd81ee6c}\.be\SetupChipset.exe' to: 'C:\ProgramData\Package Cache\{619e726e-d2b4-4e28-9568-c964fd81ee6c}\SetupChipset.exe'

[00CC:0850][2016-10-06T21:02:50]i320: Registering bundle dependency provider: {619e726e-d2b4-4e28-9568-c964fd81ee6c}, version: 10.1.1.14

[00CC:1B60][2016-10-06T21:02:50]i305: Verified acquired payload: SetupChipsetx64.msi at path: C:\ProgramData\Package Cache\.unverified\SetupChipsetx64.msi, moving to: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\SetupChipsetx64.msi.

[00CC:1B60][2016-10-06T21:02:50]i305: Verified acquired payload: cab4FADBDD6DC6637E75E196F741A3F14D1 at path: C:\ProgramData\Package Cache\.unverified\cab4FADBDD6DC6637E75E196F741A3F14D1, moving to: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\media1.cab.

[00CC:0850][2016-10-06T21:02:50]i323: Registering package dependency provider: {FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}, version: 10.1.1.14, package: SetupChipsetx64.msi

[00CC:0850][2016-10-06T21:02:50]i301: Applying execute package: SetupChipsetx64.msi, action: Repair, path: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\SetupChipsetx64.msi, arguments: ' MSIFASTINSTALL="7" IIF_MSI_SWITCHES="" ARPSYSTEMCOMPONENT="1"'

[00CC:0850][2016-10-06T21:03:11]e000: Error 0x80070643: Failed to run maintanance mode for MSI package.

[00CC:0850][2016-10-06T21:03:11]e000: Error 0x80070643: Failed to execute MSI package.

[18BC:07D4][2016-10-06T21:03:11]e000: Error 0x80070643: Failed to configure per-machine MSI package.

[18BC:07D4][2016-10-06T21:03:11]i319: Applied execute package: SetupChipsetx64.msi, result: 0x80070643, restart: None

[18BC:07D4][2016-10-06T21:03:11]e000: Error 0x80070643: Failed to execute MSI package.

[00CC:0850][2016-10-06T21:03:11]i329: Removed package dependency provider: {FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}, package: SetupChipsetx64.msi

[00CC:0850][2016-10-06T21:03:11]i351: Removing cached package: SetupChipsetx64.msi, from path: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\

[00CC:0850][2016-10-06T21:03:11]i329: Removed package dependency provider: {23312E5E-F714-4F0B-97F5-4A7E2DEFE61E}, package: SetupChipsetx86.msi

[00CC:0850][2016-10-06T21:03:11]i330: Removed bundle dependency provider: {619e726e-d2b4-4e28-9568-c964fd81ee6c}

[00CC:0850][2016-10-06T21:03:11]i352: Removing cached bundle: {619e726e-d2b4-4e28-9568-c964fd81ee6c}, from path: C:\ProgramData\Package Cache\{619e726e-d2b4-4e28-9568-c964fd81ee6c}\

[18BC:07D4][2016-10-06T21:03:11]i000: ** MBA ** Apply complete. Status: '-2147023293' Restart: 'None' Result: 'None'

[18BC:07D4][2016-10-06T21:03:11]i399: Apply complete, result: 0x80070643, restart: None, ba requested restart:  No

[18BC:0C48][2016-10-06T21:03:11]e000: ** MBA ** Unknown error.

Hope someone can help me here.

After a fresh install of Windows 8.1 Pro my media type is correctly set under the analyse and optimise function. This is using the in box drivers of Windows 8.1. When I install the latest RST and update the RAID drivers, the media type changes to SSD which is incorrect. The analyse and optimise buttons are now greyed out and I can no longer defrag the hard drives.

I have taken many steps to try and correct this issue but still no luck. The BIOS is set to UEFI and it correctly identifies the HDD. I have also used the F6 driver installation of the latest RAID driver during the Windows install. Media type is still set to SSD.

Intel RST status correctly states that SATA HDD are connected. So is it a Windows problem?

Very frustrating. Any help would be appreciated.

Surely Im not the only person in the world with this problem.

Kind Regards

System Specs

Motherboard: MSI Z87-G45

CPU: Intel 4770K

Memory: Corsair Dominator 32GB

HDD: WD Black 500GB (Raid 0) 128KB Stripe

GPU: Geforce GTX 770

I have an Skylake i5-6600K system with Asus Z170 pro gaming motherboard with the latest bios v1105, but transfer speeds from SSD to usb 3.0 external devices are terrible slow and hangs under windows 10. All the external devices are usb 3.0 and works under windows 7 very good and the transfer speeds are normal.

Things I've done.

1. Windows 10 reinstalled (same issue)

2. Bios updated to latest version v1105 (same issue)

3. Windows 10 all drivers installed (same issue)

4. under windows 7 everything working fine transfer speeds are normal.

Why is usb 3.0 under windows 10 so terrible slow and hangs. Can i conclude that this is a driver issue in windows 10.

My hardware

Cpu Intel Skylake i5-6600k

Motherboard Asus Z170 pro gaming

GPU Asus Strix GTX970

Mem crucial ballistix 16GB kit

SSD Samsung SM951 nvme 250GB

SSD Samsung 850 Evo 250GB

OS windows 10 dualboot with windows 7

USB 3.0  sharkoon quickport xt v2 docking station

External HDD usb 3.0 for backup

And some  usb 3.0 thumb drives

Het bericht is bewerkt door: Misterd I added a few screenshots.

I'm getting a shutdown bug on a Z77 Chipset. (Gigabyte g1 sniper 3)

Before my computer is shutting down i hear my harddrives just spinning on again before my PC is going off.

They do not start completely again, they are being interrupted by the shutdown then.

I tested these versions:

12.5.0.1066

12.8.0.1016

12.8.4.1000

12.8.6.1000

With the original version of windows instalacion (12.0.1.1019), this bug not appear.

I updated Orom of the Main Board to 12.7.0.1936 but some error appear of shutdown.

In Bios, Sata it´s configured at RAID mode

Windows 8 or 8.1 - OS makes no difference. Fresh instalation to test diferent version drivers.

x2 SSD M4-CT128M4SSD2 RAID-0

x2 HDDs ST500DM002 RAID-0

x2 HDDs ST3250620AS

Can help me?

A Greeting

PS: 12.8.0.1016 (the release offered officially by the motherboard manufacturer, already double-checked this file (SetupRST.exe) matches the one downloaded from downloadcenter.intel.com)

El mensaje fue editado por: Ra·l E. Added more information. PS

Hi,

I have an issue with the Intel Extreme Tuning Utility, the latest version. (6.1.2.13)

I could not get it to install, latest windows 10 (build 14393) I kept getting getting an error saying could not start the XTU service, verify you have sufficient privileges.

I got frustrated, so I re-installed windows to remove any old versions or conflicts.  Then once windows and drivers were fully patched I tried the XTU install again, but got the same error.

In Windows Services I noted that XTU was listed as starting. I noted that in resource monitor the Intel integrated clock controller service ICCS was using a bit of CPU.

When i manually stopped the ICCS the XTU started just fine, then I could start the XTU without a drama, and the install completed without error.

Now each time I startup the PC the XTU does not start. it will start when I manually stop the ICCS.

The board is an ASrock Z170 Pro 4, with the latest BIOS, 7.0.

As far as I understand, Intel RST drivers up to version 14.8 still don't support Smart Response Technology in Windows 10.

This is becoming a serious issue for me as a computer builder. I have dozens of clients who have upgraded from 8.1 to 10 and lost their SSD caching functionality. I was a real supporter of SRT because it made it easy for novice users not to fill up a small SSD and sold many computers with SRT.

I've promised them all that I'll fix this issue as soon as Intel releases drivers that support this feature in Windows 10 but as of today this hasn't happened. I made that promise in August. It's been more than six months now and some of my clients are becoming very displeased with me. I've basically already lost some clients because their computers have become too slow, forcing me to install full fledged SSDs at my expense or downgrade them back to 8.1, in hope not to lose them.

What's the deal here? Is Intel ever going to release drivers that enable SRT in Windows 10? You had a year of time. I'm starting to think that this feature is never going to come to 10 which is crazy since it's still advertised on your website.