- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello everyone,
We are trying to install Intel_GFX101.4953 in silent mode via MS Intune.
We tried cmd and also PS scripts, packaged in a win32-app.
The script is working with admin-rights on a local machine.
When we package the scripts as a win32 app, the Installer.exe hangs and don't finish the process.
The log file is filled as follows:
2023/11/30 18:34:30.380|INFO|Logging started on 2023/11/30 18:34:30.344 ||
2023/11/30 18:34:30.393|INFO|Installer version: 1.0.737.0 ||
2023/11/30 18:34:30.393|INFO|Installer executable path: "C:\windows\IMECache\7224f2e4-d4bd-4fde-96f9-207f6948_1\Installer.exe" ||
2023/11/30 18:34:30.393|INFO|Installer root directory: "C:\windows\TEMP\.net\Installer\0siVqCyBTLYBZCEYpqNBmjXHF7dVgsI=\" ||
2023/11/30 18:34:30.393|INFO|Command line arguments: --overwrite --silent --report C:\intel.log ||
2023/11/30 18:34:30.393|INFO|Language of the user interface: [de-DE] ||
2023/11/30 18:34:30.396|INFO|Operating system specification: Microsoft Windows NT 10.0.19045.0 ||
2023/11/30 18:34:30.450|INFO|CPU base clock: 2592Mhz ||
2023/11/30 18:34:30.450|INFO|Test Signing: OFF ||
2023/11/30 18:34:30.450|INFO|Windows Media Player status: Installed ||
2023/11/30 18:34:30.450|INFO|Non-Interactive mode flag: True ||
2023/11/30 18:34:30.450|INFO|Setting admin access rights - Directory: C:\windows\TEMP\.net\Installer\0siVqCyBTLYBZCEYpqNBmjXHF7dVgsI=\. ||
2023/11/30 18:34:30.501|INFO|Setting admin access rights - DONE ||
Can anyone here possibly help?
We urgently need to replace the drivers because Lenovo pushed faulty drivers via Lenovo Vantage.
However, Lenovo hasn't offered any newer drivers for 2 weeks.
Thanks alot.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, @dieseasdea
Thank you for posting on the Intel® communities.
I understand it can be frustrating having installation issues in a moment like this, I will do my best to assist you here.
Please attach an Intel SSU report from one of the computers with problems so we can have more information about these systems:
Intel® System Support Utility for Windows.
Note: Make sure to mark the box that says "everything" before pressing the Scan button. After that, click on "Next>" and select "Save" and then, attach the .txt file.
Best regards,
Jocelyn M.
Intel Customer Support Technician.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, @dieseasdea
I hope you are great.
I am checking this thread and I would like to know if you were able to check my previous post.
Best regards,
Jocelyn M.
Intel Customer Support Technician.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, @dieseasdea
I hope you are doing great.
As we have not heard back from you, we will proceed to close this thread now.
If you need any further assistance, please feel free to contact us back and submit a new question as this thread will no longer be monitored.
Best regards,
Jocelyn M.
Intel Customer Support Technician.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @Jocelyn_Intel
i tried also to deploy the current Intel driver https://www.intel.com/content/www/us/en/download/785597/833969/intel-arc-iris-xe-graphics-windows.html over Intune and experienced the same behaviour.
I tried to install the gfx_win_101.6078.exe direct with the '-s -o -f' installation switches and also extracted the gfx and tried to install direct the installer.exe also with the '-s -o -f' installation switches. The bahaviour is the same.
I can see the installer process has been started but seems to be inactive. The intelGFX.log is showing following enties:
2024/10/10 18:15:58.657|INFO|Logging started on 2024/10/10 18:15:58.647 ||
2024/10/10 18:15:58.663|INFO|Attaching console to parent process - DONE ||
2024/10/10 18:15:58.687|INFO|Scanning for hardware changes ||
2024/10/10 18:15:59.992|INFO|Installer version: 1.0.962.4 ||
2024/10/10 18:15:59.992|INFO|Installer initial executable path: "C:\WINDOWS\IMECache\c72923f4-b3be-4925-8900-658d9069d7dd_8\Installer.exe" ||
2024/10/10 18:15:59.992|INFO|Installer main executable path: "C:\WINDOWS\SystemTemp\Intel\Installer\Installer.exe" ||
2024/10/10 18:15:59.992|INFO|Installer parent process module path: "C:\WINDOWS\IMECache\c72923f4-b3be-4925-8900-658d9069d7dd_8\Installer.exe" ||
2024/10/10 18:16:00.009|INFO|Installer startup type: WindowsPowerShell ||
2024/10/10 18:16:00.009|INFO|Installer root directory: "C:\WINDOWS\SystemTemp\Intel\Installer\" ||
2024/10/10 18:16:00.009|INFO|Command line arguments: -s -o -f ||
2024/10/10 18:16:00.009|INFO|Language of the user interface: [en-US] ||
2024/10/10 18:16:00.009|INFO|Operating system specification: Microsoft Windows NT 10.0.26100.0 ||
2024/10/10 18:16:00.009|INFO|Operating system boot time: 2024-10-10 18:08:22 ||
2024/10/10 18:16:00.066|INFO|CPU base clock: 3600Mhz ||
2024/10/10 18:16:00.066|INFO|Test Signing: OFF ||
2024/10/10 18:16:00.066|INFO|Windows Media Player status: Installed ||
2024/10/10 18:16:00.066|INFO|Non-Interactive mode flag: True ||
2024/10/10 18:16:00.102|INFO|Bitlocker protection status: PROTECTION_ON ||
2024/10/10 18:16:00.103|INFO|Setting admin access rights - Directory: C:\WINDOWS\SystemTemp\Intel\Installer\. ||
2024/10/10 18:16:00.103|INFO|Setting admin access rights - DONE ||
Attached you can find also the SSU logs.
I hope you can provide me a solution for this problem.
Best regards,
Alex
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is a known issue where the Intel driver package does not allow to be installed from C:\Windows\SystemTemp due to a policy of the package.
This basically stops the package from being usable in a software deployment solution like SCCM or Intune where the packages are installed in the System context.
This was raised in an Intel support case that I raised a few months ago where Intel advised that this would be fixed in a future release but could take a few months to get done.
If it's any help for Intel staff on this forum, the case ID is #06320352.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page