installation of WIN10_64 - Step_1 drivers fails

Henk Ringersma

When installing the WIN10_64 - Step_1 driver as an Administrator (or not), the process fails with error:
"The requested operation failed, A system reboot is required to roll back changes made"
The log file I have attached.

Please help

---

last part of log file ----
09:17:51:480: Reading config file : C:\drivers WIN10_64\WIN10_64\Step_1-Chipset_and_peripherals\WIN10_64\Config.xml
09:17:51:572: Read SocPackageInfo Version : 0x1
09:17:51:587: Reading string value
09:17:51:619: Read XML SocPackageInfo Root : HKEY_LOCAL_MACHINE, Key : SOFTWARE\Intel\SOCPackageInfo, Value : VersionNumber, Version string name : Version, version string : 102
09:17:51:634: Registry key SOFTWARE\Intel\SOCPackageInfo does not exist or can not be read. Error : Unable to read registry value : VersionNumber - Error Code : 2. Assuming the installed version is oldest. Proceeding with installation.
09:17:51:656: Preparing UI
09:17:51:687: Reading config file : C:\drivers WIN10_64\WIN10_64\Step_1-Chipset_and_peripherals\WIN10_64\Config.xml
09:17:51:703: Read Title Override : Intel x64 CherryTrail-T Driver Package
09:17:51:734: Reading config file : C:\drivers WIN10_64\WIN10_64\Step_1-Chipset_and_peripherals\WIN10_64\Config.xml
09:17:51:756: Read Title Override : Intel x64 CherryTrail-T Driver Package
09:17:51:787: Showing dialog: WELCOME
09:19:32:695: Showing dialog: LICENSE
09:20:08:878: Showing dialog: CONFIRM
09:20:37:757: Started installation thread
09:20:37:778: Setup mode
09:20:37:794: Showing dialog: PROGRESS
09:20:38:010: Read registry subkey Code and value 2
09:20:38:041: Read registry subkey Reboot and value 0
09:20:38:063: E Unable to pre-install driver file : C:\drivers WIN10_64\WIN10_64\Step_1-Chipset_and_peripherals\WIN10_64\Drivers\MBI\MBI.inf - error code : 2
09:20:38:079: E Uninstalling drivers that were previously pre-installed by DriverPackagePreInstall...
09:20:38:094: E Setup aborted!
09:20:38:125: m_nCurrentIndex : 4
09:20:38:178: Showing dialog: FINISH

Jacky Kuo

Looks "WIN10_64 - Step_1 driver" folder name causes this problem.
Please move entire "WIN10_64" folder to Desktop then try to install driver.

Jacky Kuo

Looks "drivers WIN10_64" or "Step_1-Chipset_and_peripherals" folder name causes this problem.
Please move entire "WIN10_64" folder to Desktop then try to install driver.

Henk Ringersma

Thanks. That helped!
I guess no spaces are allowed in the folder names for Step_1 drivers.

Fabio

Hello to all
I have the same problem
I have tried it as in the photo but the problem remains.

Can you help me, please?
Thank you

rogertsai(AAEON)

In most cases, installing the Intel® CherryTrail-T driver goes smoothly and turns out to be a success.
In your case, please follow the steps below to check for your UP board
1. Back to bios, and restore defaults
2. The driver package re-download again
>> To UP-Board
>> To UP-Squared
3. reinstall the driver package again

And what is your BIOS version?

Fabio

Hello
For up2 kikstarted , should I use To UP-Board or To UP-Squared?
I have a up2 and install To UP-Board .
I use Up-APL01 R1.8 UPA1AM18 0f 06/23/2017
The last bios is ?
Thanks

This is log file

2017:09:17 18:41:50:621:
2017:09:17 18:41:50:637: >>> Log start
2017:09:17 18:41:50:637: Mutex with given name doesn't exist. Creating new one.

2017:09:17 18:41:50:653: Obtained mutex succesfully.
2017:09:17 18:41:50:653: Single-instance mutex has been obtained
2017:09:17 18:41:50:653: Core version: 2.5.48
2017:09:17 18:41:50:668: Setup version: 2.0.29.0
2017:09:17 18:41:50:668: Command line: "D:\20160307\Step2-TXE\SetupTXE.exe"
2017:09:17 18:41:50:684: OS data: 6-2-1-0 64-bit
2017:09:17 18:41:50:699: System up time: 200 sec
2017:09:17 18:41:50:699: Reboot pending: No
2017:09:17 18:41:50:715: Current UI language: 0410
2017:09:17 18:41:50:731: Language folder: C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp
2017:09:17 18:41:50:793: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\ar-SA\IntelCommon.dll. Lang 0401. Rank 0
2017:09:17 18:41:50:871: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\cs-CZ\IntelCommon.dll. Lang 0405. Rank 0
2017:09:17 18:41:50:934: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\da-DK\IntelCommon.dll. Lang 0406. Rank 0
2017:09:17 18:41:50:981: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\de-DE\IntelCommon.dll. Lang 0407. Rank 0
2017:09:17 18:41:51:043: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\el-GR\IntelCommon.dll. Lang 0408. Rank 0
2017:09:17 18:41:51:106: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\en-US\IntelCommon.dll. Lang 0409. Rank 1
2017:09:17 18:41:51:168: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\es-ES\IntelCommon.dll. Lang 0C0A. Rank 0
2017:09:17 18:41:51:231: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\fi-FI\IntelCommon.dll. Lang 040B. Rank 0
2017:09:17 18:41:51:293: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\fr-FR\IntelCommon.dll. Lang 040C. Rank 0
2017:09:17 18:41:51:356: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\he-IL\IntelCommon.dll. Lang 040D. Rank 0
2017:09:17 18:41:51:403: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\hu-HU\IntelCommon.dll. Lang 040E. Rank 0
2017:09:17 18:41:51:465: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\it-IT\IntelCommon.dll. Lang 0410. Rank 3
2017:09:17 18:41:51:528: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\ja-JP\IntelCommon.dll. Lang 0411. Rank 0
2017:09:17 18:41:51:575: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\ko-KR\IntelCommon.dll. Lang 0412. Rank 0
2017:09:17 18:41:51:637: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\nb-NO\IntelCommon.dll. Lang 0414. Rank 0
2017:09:17 18:41:51:684: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\nl-NL\IntelCommon.dll. Lang 0413. Rank 0
2017:09:17 18:41:51:746: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\pl-PL\IntelCommon.dll. Lang 0415. Rank 0
2017:09:17 18:41:51:809: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\pt-BR\IntelCommon.dll. Lang 0416. Rank 0
2017:09:17 18:41:51:871: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\pt-PT\IntelCommon.dll. Lang 0816. Rank 0
2017:09:17 18:41:51:934: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\ru-RU\IntelCommon.dll. Lang 0419. Rank 0
2017:09:17 18:41:51:996: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\sk-SK\IntelCommon.dll. Lang 041B. Rank 0
2017:09:17 18:41:52:059: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\sl-SI\IntelCommon.dll. Lang 0424. Rank 0
2017:09:17 18:41:52:121: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\sv-SE\IntelCommon.dll. Lang 041D. Rank 0
2017:09:17 18:41:52:184: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\th-TH\IntelCommon.dll. Lang 041E. Rank 0
2017:09:17 18:41:52:246: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\tr-TR\IntelCommon.dll. Lang 041F. Rank 0
2017:09:17 18:41:52:309: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\zh-CN\IntelCommon.dll. Lang 0804. Rank 0
2017:09:17 18:41:52:356: Found C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp\zh-TW\IntelCommon.dll. Lang 0404. Rank 0
2017:09:17 18:41:52:387: Loading language 0410
2017:09:17 18:41:52:403: Setup mode: Installation
2017:09:17 18:41:52:418: Looking for OS: 6.1.1 6.2
2017:09:17 18:41:52:434: OS check passed
2017:09:17 18:41:52:450: .NET not required, skipping requirement check
2017:09:17 18:41:52:450: Resolving driver source
2017:09:17 18:41:52:465: Using embedded driver(s). Temp source is 'C:\Users\SERVER~1\AppData\Local\Temp\IIF1714.tmp'
2017:09:17 18:41:52:606: Using folder 'C:\Users\SERVER~1\AppData\Local\Temp\IIF1714.tmp' as the driver source
2017:09:17 18:41:52:622: Scanning all active devices
2017:09:17 18:41:52:637: Scanning x64\TXEI.inf (Name: TXEI64, Version: 2.0.0.1067)
2017:09:17 18:41:52:653: Section with the best match: Intel.NTamd64.6.1
2017:09:17 18:41:52:668: Device: PCI\VEN_8086&DEV_2298 (Intel(R) Trusted Execution Engine Interface )
2017:09:17 18:41:52:684: MUP OS bits: 0xB6C00
2017:09:17 18:41:52:684: Scanning x86\TXEI.inf (Name: TXEI32, Version: 2.0.0.1067)
2017:09:17 18:41:52:700: No section match
2017:09:17 18:41:52:715: MUP OS bits: 0x49200
2017:09:17 18:41:52:731: E Win32 exception occurred!!
2017:09:17 18:41:52:731: Error code: 0x4E24 (20004)
2017:09:17 18:41:52:747: Error text: ''
2017:09:17 18:41:52:762: Extended error text: 'Error in device matching'
2017:09:17 18:41:52:778: Debug info: 'Setup.cpp (257)'
2017:09:17 18:41:52:778: Reading storyboard
2017:09:17 18:41:52:793: Page count: 7
2017:09:17 18:41:52:809: Added: Welcome
2017:09:17 18:41:52:825: Added: Modify
2017:09:17 18:41:52:825: Added: License
2017:09:17 18:41:52:840: Added: Confirm
2017:09:17 18:41:52:856: Added: Progress
2017:09:17 18:41:52:856: Added: Finish
2017:09:17 18:41:52:872: Added: Error
2017:09:17 18:41:52:887: Reading string map
2017:09:17 18:41:52:903: No string map present
2017:09:17 18:41:52:981: Showing page: Error
2017:09:17 18:41:58:256: Link: Launching 'C:\Users\SERVERmicro\Intel\Logs'
2017:09:17 18:42:04:444: Dumping properties (25 total)
2017:09:17 18:42:04:460: IIF_MSILOGLEVEL=4096
2017:09:17 18:42:04:475: INSTALL_TXEI=1
2017:09:17 18:42:04:491: INSTALL_DAL=1
2017:09:17 18:42:04:506: INSTALL_TCS=1
2017:09:17 18:42:04:522: INSTALL_SPE=1
2017:09:17 18:42:04:538: IIF_LOGFOLDER=C:\Users\SERVERmicro\Intel\Logs
2017:09:17 18:42:04:538: IIF_SETUPVERSION=2.0.29.0
2017:09:17 18:42:04:553: IIF_PACKAGEVERSION=2.0.0.1067
2017:09:17 18:42:04:569: IIF_SETUPPATH=D:\20160307\Step2-TXE
2017:09:17 18:42:04:585: IIF_CACHELOC=C:\ProgramData\Intel\Package Cache\{176E2755-0A17-42C6-88E2-192AB2131278}
2017:09:17 18:42:04:600: IIF_OS=10.0
2017:09:17 18:42:04:616: IIF_DEBUG_REPORTEDVERSION=6.2
2017:09:17 18:42:04:632: IIF_OSSERVICEPACK=0
2017:09:17 18:42:04:632: IIF_IS64=1
2017:09:17 18:42:04:647: IIF_NET40CLIENT=1
2017:09:17 18:42:04:663: IIF_NET40FULL=1
2017:09:17 18:42:04:678: IIF_NET45CLIENT=1
2017:09:17 18:42:04:694: IIF_NET45FULL=1
2017:09:17 18:42:04:710: IIF_INSTALLFOLDER=C:\Program Files\Intel\TXE Components
2017:09:17 18:42:04:710: IIF_LANGCOUNTRY=it-IT
2017:09:17 18:42:04:725: IIF_RESOURCEFOLDER=C:\Users\SERVER~1\AppData\Local\Temp\IIF104D.tmp
2017:09:17 18:42:04:741: IIF_SETUPMODE=INSTALL
2017:09:17 18:42:04:757: IIF_EXITCODE=1602
2017:09:17 18:42:04:772: IIF_LICENSE=
2017:09:17 18:42:04:772: IIF_README=
2017:09:17 18:42:04:788: Dumping feature states
2017:09:17 18:42:04:803: Feature: 'DriverFeature' | Package: '{B75FA462-A375-4F12-AF79-ACB6D79E60F2}' | Current: 'false' | New: 'false'
2017:09:17 18:42:04:819: Feature: 'DALFeature' | Package: '{BBCD444B-4502-4301-A21B-FE61006E72B4}' | Current: 'false' | New: 'false'
2017:09:17 18:42:04:835: Feature: '' | Package: '{BBCD444B-4502-4301-A21B-FE61006E72B4}' | Current: 'false' | New: 'false'
2017:09:17 18:42:04:835: Feature: 'TCSFeature' | Package: '{BBCD444B-4502-4301-A21B-FE61006E72B4}' | Current: 'false' | New: 'false'
2017:09:17 18:42:04:850: Feature: 'ALL' | Package: '{DAB2D6B9-54CE-4225-B2C6-0535AEEF18A9}' | Current: 'false' | New: 'false'
2017:09:17 18:42:04:866: Exit code (command line): 1602
2017:09:17 18:42:04:882: >>> Log End

rogertsai(AAEON)

UP2 = UP-Squared, so you should use UP-Squared drive on your UP2 board
click here to download the UP2-windows 10 driver

and the last version is UPA1AM21, please click the link below for UP2 BIOS
UP2-uefi-BIOS

Fabio

Ok thanks @roger1tsai

but I have two new problems >

1) There are no bios files on your page

2)Installing all Windows 10 drivers and updating does not yet recognize 5 peripherals: audio, pci, and 3 unknown peripherals

David Rolfe

roger1tsai wrote:

.....and the last version is UPA1AM21, please click the link below for UP2 BIOS
UP2-uefi-BIOS

Unfortunately the file (and instructions) appear to have 'vanished' for the moment!

Hopefully they will quickly be restored!

Fabio

Hello @Montala

OK thanks for your confirmation.
Do you know how to fix my missing driver problem?
Thank you

David Rolfe

Hi ninoo,

Not immediately, I'm afraid, but hopefully once the BIOS files are available again, which I am sure they will be fairly quickly, and you have been able to update the BIOS on your board, then the procedures outlined above in posts from roger1tsai will be of some help to you.