Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Republic of Gamers Forum
- ROG Care
- Hardware & Software Support
- Previous Forum
- Re: Harmful deloeminf.ps1 script in latest ASUS In...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Harmful deloeminf.ps1 script in latest ASUS Intel I225/226 LAN Driver
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
03-03-2023 11:53 PM
N.B. This does not apply to the latest Intel I225/226 driver redistributed by MoKiChU, as far as I can see. It only applies to ASUS-packaged drivers containing a file named deloeminf.ps1; if that file is not included, this does not apply. So far, I've only seen the problem in the 1.1.4.38/2.1.3.3 download from March; the 2.1.2.3 download from December did not have this problem.
The latest ASUS-packaged Intel I225/226 LAN driver (DRV_LAN_Intel_I225_I226_TSD_W11_64_V11438_20230303R.zip, found on the Crosshair X670E Extreme downloads, for example) contains a harmful deloeminf.ps1 script which can do a bit of a hatchet job on completely unrelated drivers. As far as I can tell, this is an ASUS thing rather than an Intel thing, as these scripts have never been present in the drivers published directly by Intel. Here is the script in question:
The problem is that this script will match any oem*.inf file containing the string "e2f" (also, the second case will never execute, as it tries to match "e2f68" after that has been captured by the first case, but that doesn't really matter for this purpose). This matches far more than just older versions of the I225/I226 driver, some of which are completely unrelated. E.g. it will match "ClassGuid = {e2f84ce7-8efa-411c-aa69-97454ca4cb57}", which has nothing to do with Intel LAN drivers; causing the script to nuke some/all of the audio drivers on my system (if I was to run it, which I didn't). Basically, it matches both Intel e2f drivers and any oem*.inf which happens to contain "e2f" in a hexadecimal number (e.g. GUIDs, PCI IDs, USB IDs, registry values, etc).
This is a recent change to the ASUS scripts/installer, as the older OEMFILE.CMD implementation (e.g. DRV_LAN_Intel_I226_Cx_TP_W11_64_V2123_20221219R.zip found on the Crosshair VIII Extreme downloads) was relatively safe, using:
That could still be improved a little bit by using "%windir%" instead of hard coding "C:\Windows", but that wouldn't cause it to do any serious harm when running on an unusual installation (it just wouldn't uninstall the older drivers). It has an extremely low chance of falsely matching and deleting some other driver, really only if some other vendor happened to use the same driver name.
A quick fix for the new deloeminf.ps1 script would be to make the match more specific, e.g.
That combines the two cases into one by using a regular expression instead of "-SimpleMatch".
Better still, although a little slower to run, would be to use native PowerShell objects to match in a more powerful and precise way. E.g.
Moving over to PowerShell is basically a good thing, as it's so much more powerful than the old batch files, but you need to do more than a minimalist translation from batch scripts to do it properly and safely. The majority of Windows has a full object interface in PowerShell, allowing so much more than was possible with older methods. It's generally far better to use the proper object interfaces rather than just translate the old methods directly.
The latest ASUS-packaged Intel I225/226 LAN driver (DRV_LAN_Intel_I225_I226_TSD_W11_64_V11438_20230303R.zip, found on the Crosshair X670E Extreme downloads, for example) contains a harmful deloeminf.ps1 script which can do a bit of a hatchet job on completely unrelated drivers. As far as I can tell, this is an ASUS thing rather than an Intel thing, as these scripts have never been present in the drivers published directly by Intel. Here is the script in question:
$oemfiles = gci $ENV:windir\inf\oem*.inf
foreach($file in $oemfiles)
{
if (get-content $file | select-string -pattern 'e2f' -SimpleMatch)
{
.\devcon.exe dp_delete $file.name
}
elseif (get-content $file | select-string -pattern 'e2f68' -SimpleMatch)
{
.\devcon.exe dp_delete $file.name
}
}
The problem is that this script will match any oem*.inf file containing the string "e2f" (also, the second case will never execute, as it tries to match "e2f68" after that has been captured by the first case, but that doesn't really matter for this purpose). This matches far more than just older versions of the I225/I226 driver, some of which are completely unrelated. E.g. it will match "ClassGuid = {e2f84ce7-8efa-411c-aa69-97454ca4cb57}", which has nothing to do with Intel LAN drivers; causing the script to nuke some/all of the audio drivers on my system (if I was to run it, which I didn't). Basically, it matches both Intel e2f drivers and any oem*.inf which happens to contain "e2f" in a hexadecimal number (e.g. GUIDs, PCI IDs, USB IDs, registry values, etc).
This is a recent change to the ASUS scripts/installer, as the older OEMFILE.CMD implementation (e.g. DRV_LAN_Intel_I226_Cx_TP_W11_64_V2123_20221219R.zip found on the Crosshair VIII Extreme downloads) was relatively safe, using:
find /i "CatalogFile = e2f.cat" C:\Windows\inf\%_OEMFILE%
That could still be improved a little bit by using "%windir%" instead of hard coding "C:\Windows", but that wouldn't cause it to do any serious harm when running on an unusual installation (it just wouldn't uninstall the older drivers). It has an extremely low chance of falsely matching and deleting some other driver, really only if some other vendor happened to use the same driver name.
A quick fix for the new deloeminf.ps1 script would be to make the match more specific, e.g.
$oemfiles = gci $ENV:windir\inf\oem*.inf
foreach($file in $oemfiles)
{
if (get-content $file | select-string -pattern 'CatalogFile\s*=\s*e2f(68|n)?.cat')
{
.\devcon.exe dp_delete $file.name
}
}
That combines the two cases into one by using a regular expression instead of "-SimpleMatch".
Better still, although a little slower to run, would be to use native PowerShell objects to match in a more powerful and precise way. E.g.
Get-WindowsDriver -Online -All | Where-Object {
$_.Driver -Like 'oem*' -and
$_.OriginalFileName -match '\\e2f(68|n)?\.inf$' -and
$_.ClassName -eq 'Net' -and
$_.ProviderName -eq 'Intel'
}Moving over to PowerShell is basically a good thing, as it's so much more powerful than the old batch files, but you need to do more than a minimalist translation from batch scripts to do it properly and safely. The majority of Windows has a full object interface in PowerShell, allowing so much more than was possible with older methods. It's generally far better to use the proper object interfaces rather than just translate the old methods directly.
Labels:
- Labels:
-
Previous Forum
1,882 Views
7 REPLIES 7
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
03-06-2023 05:03 PM
Hello, Murph_9000.
Thank you for sharing the information.
Before consulting with relevant departments, please help confirm the following questions:
- What is the motherboard model and BIOS version you are currently using? What is the BIOS setting?
- When installing the driver released in March, did you encounter any abnormalities in use?
For example, an unstable network or being disconnected.
If so, what are the frequency and circumstances of the occurrence? Please provide screenshots, if any.
- the brand and model name of the CPU, DRAM, GPU, and PSU currently installed, as well as the OS version and OS build
The above information can help the related team pick up and check the problem faster.
Thank you.
Thank you for sharing the information.
Before consulting with relevant departments, please help confirm the following questions:
- What is the motherboard model and BIOS version you are currently using? What is the BIOS setting?
- When installing the driver released in March, did you encounter any abnormalities in use?
For example, an unstable network or being disconnected.
If so, what are the frequency and circumstances of the occurrence? Please provide screenshots, if any.
- the brand and model name of the CPU, DRAM, GPU, and PSU currently installed, as well as the OS version and OS build
The above information can help the related team pick up and check the problem faster.
Thank you.
Due to the ongoing regional holidays, my responses may be slightly delayed.
Thank you in advance for your patience 🙂
Thank you in advance for your patience 🙂
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
03-06-2023 08:57 PM
Hi there. Just to be clear, this is really a bug report rather than a support request (this was just the best place I could find to file a non-security report). The script will misbehave on all systems. I'm happy to give those details, just want to emphasise that this is not specific to my system or components.
Crosshair VIII Extreme, BIOS 1101, optimised defaults + DOCP
I didn't run the ASUS installer for the March driver, as I spotted the bug prior to any installation attempt. I have a habit of looking through the installer scripts prior to installing drivers from a mixture of curiosity and a "trust but verify" mindset. I just simulated the PowerShell code in my head to spot the erroneous behaviour, then confirmed it by running a test script which followed the same pattern but did not make any system changes.
I've not been having any disconnection issues with my motherboard's I225-V, and it has always been generally stable.
CPU: 5950X-B2
DRAM: Crucial BL16G36C16U4B.M16FE1
GPU: Strix RX 6750 XT OC
PSU: Thor 1200W
OS: Windows 11 Pro 22H2 version 10.0.22621 build 22621
Here's a test / diagnostic PowerShell script following the same general pattern of the deloeminf.ps1 script in the driver. It uses the same selection criteria, doesn't make any changes to drivers, and lists the drivers which would have been deleted by the original script. It first provides a directory type listing, then the output will pause for a little while as the Windows DISM subsystem enumerates all drivers on the system, then it will output a detailed list of all of the impacted drivers. It should run on any Windows 11 system, requires an Administrator PowerShell for Get-WindowsDriver, and the list of drivers output will vary depending on the specific system and what happens to have "e2f" somewhere in the installed oem*.inf file.
Sample output from the above on my system (these are all of the drivers which would have been erroneously deleted by the original script):
Crosshair VIII Extreme, BIOS 1101, optimised defaults + DOCP
I didn't run the ASUS installer for the March driver, as I spotted the bug prior to any installation attempt. I have a habit of looking through the installer scripts prior to installing drivers from a mixture of curiosity and a "trust but verify" mindset. I just simulated the PowerShell code in my head to spot the erroneous behaviour, then confirmed it by running a test script which followed the same pattern but did not make any system changes.
I've not been having any disconnection issues with my motherboard's I225-V, and it has always been generally stable.
CPU: 5950X-B2
DRAM: Crucial BL16G36C16U4B.M16FE1
GPU: Strix RX 6750 XT OC
PSU: Thor 1200W
OS: Windows 11 Pro 22H2 version 10.0.22621 build 22621
Here's a test / diagnostic PowerShell script following the same general pattern of the deloeminf.ps1 script in the driver. It uses the same selection criteria, doesn't make any changes to drivers, and lists the drivers which would have been deleted by the original script. It first provides a directory type listing, then the output will pause for a little while as the Windows DISM subsystem enumerates all drivers on the system, then it will output a detailed list of all of the impacted drivers. It should run on any Windows 11 system, requires an Administrator PowerShell for Get-WindowsDriver, and the list of drivers output will vary depending on the specific system and what happens to have "e2f" somewhere in the installed oem*.inf file.
$oemfiles = gci $ENV:windir\inf\oem*.inf
$drivers = @();
foreach ($file in $oemfiles) {
if ($str = (Get-Content $file | Select-String -Pattern 'e2f' -SimpleMatch)) {
$drivers += $file
}
}
$drivers
Get-WindowsDriver -Online -All | Where-Object Driver -In $drivers.name
Sample output from the above on my system (these are all of the drivers which would have been erroneously deleted by the original script):
PS C:\WINDOWS\system32> C:\Users\Murph\OneDrive\Documents\deloeminf-demo.ps1
Directory: C:\WINDOWS\inf
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 06/10/2022 05:12 391808 oem102.inf
-a---- 06/10/2022 05:12 27926 oem103.inf
-a---- 21/12/2022 02:01 766012 oem108.inf
-a---- 24/01/2023 09:58 929205 oem110.inf
-a---- 24/01/2023 09:58 26963 oem111.inf
-a---- 24/01/2023 09:58 12018 oem112.inf
-a---- 24/01/2023 20:52 30150 oem115.inf
-a---- 12/10/2022 20:12 460292 oem118.inf
-a---- 16/02/2023 14:28 400022 oem12.inf
-a---- 12/10/2022 20:12 548758 oem120.inf
-a---- 06/10/2022 05:12 12865 oem17.inf
-a---- 23/02/2023 20:57 577390 oem19.inf
-a---- 06/10/2022 05:12 394895 oem20.inf
-a---- 06/10/2022 05:12 2885 oem31.inf
-a---- 21/12/2022 06:15 104375 oem5.inf
-a---- 06/10/2022 05:12 1612 oem51.inf
-a---- 06/10/2022 05:12 1673 oem58.inf
-a---- 06/10/2022 05:12 22640 oem6.inf
-a---- 06/10/2022 05:12 23570 oem61.inf
-a---- 06/10/2022 05:12 85939 oem65.inf
-a---- 06/10/2022 05:12 11696 oem71.inf
-a---- 04/03/2023 06:28 104375 oem74.inf
-a---- 06/10/2022 05:12 663240 oem78.inf
-a---- 21/01/2023 17:14 12910 oem86.inf
-a---- 21/12/2022 02:01 396390 oem88.inf
-a---- 06/10/2022 05:12 12910 oem93.inf
Driver : oem102.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\netwtw6e.inf_amd64_4f9649e16912146d\netwtw
6e.inf
InBox : False
CatalogFile : Netwtw6e.cat
ClassName : net
ClassGuid : {4D36E972-E325-11CE-BFC1-08002BE10318}
ClassDescription : Network adapters
BootCritical : False
DriverSignature : Signed
ProviderName : Intel
Date : 14/08/2022 00:00:00
Version : 22.150.0.4
Driver : oem103.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\realtekservice.inf_amd64_7f98f584c61c8c61\
realtekservice.inf
InBox : False
CatalogFile : RealtekService.cat
ClassName : SoftwareComponent
ClassGuid : {5C4C3332-344D-483C-8739-259E934C9CC8}
ClassDescription : Software components
BootCritical : False
DriverSignature : Signed
ProviderName : Realtek
Date : 09/11/2021 00:00:00
Version : 1.0.0.454
Driver : oem108.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\netwtw08.inf_amd64_52ea7835e4a6695c\netwtw
08.inf
InBox : False
CatalogFile : Netwtw08.cat
ClassName : net
ClassGuid : {4D36E972-E325-11CE-BFC1-08002BE10318}
ClassDescription : Network adapters
BootCritical : False
DriverSignature : Signed
ProviderName : Intel
Date : 23/11/2022 00:00:00
Version : 22.190.0.4
Driver : oem110.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\dtsapo4ultraasusextensionpkg.inf_amd64_614
25c16845244f5\dtsapo4ultraasusextensionpkg.inf
InBox : False
CatalogFile : dtsapo4ultraAsusextensionpkg.cat
ClassName : Extension
ClassGuid : {E2F84CE7-8EFA-411C-AA69-97454CA4CB57}
ClassDescription : Extensions
BootCritical : False
DriverSignature : Signed
ProviderName : DTS
Date : 17/08/2022 00:00:00
Version : 1.11.6.0
Driver : oem111.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\avolutess3ext.inf_amd64_0876889bd9814307\a
volutess3ext.inf
InBox : False
CatalogFile : AVoluteSS3Ext.cat
ClassName : Extension
ClassGuid : {E2F84CE7-8EFA-411C-AA69-97454CA4CB57}
ClassDescription : Extensions
BootCritical : False
DriverSignature : Signed
ProviderName : A-Volute
Date : 13/07/2022 00:00:00
Version : 1.3.18.0
Driver : oem112.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\extrtxusb_asus_avo_rtk.inf_amd64_6aae0fd7e
ac43a04\extrtxusb_asus_avo_rtk.inf
InBox : False
CatalogFile : ExtRtXUsb.cat
ClassName : Extension
ClassGuid : {E2F84CE7-8EFA-411C-AA69-97454CA4CB57}
ClassDescription : Extensions
BootCritical : False
DriverSignature : Signed
ProviderName : Realtek
Date : 18/08/2022 00:00:00
Version : 1.0.0.66
Driver : oem115.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\realtekservice.inf_amd64_4c10eeff886a3252\
realtekservice.inf
InBox : False
CatalogFile : RealtekService.cat
ClassName : SoftwareComponent
ClassGuid : {5C4C3332-344D-483C-8739-259E934C9CC8}
ClassDescription : Software components
BootCritical : False
DriverSignature : Signed
ProviderName : Realtek
Date : 13/09/2022 00:00:00
Version : 1.0.560.0
Driver : oem118.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\netwtw06.inf_amd64_10dbb026a21af87e\netwtw
06.inf
InBox : False
CatalogFile : Netwtw06.cat
ClassName : net
ClassGuid : {4D36E972-E325-11CE-BFC1-08002BE10318}
ClassDescription : Network adapters
BootCritical : False
DriverSignature : Signed
ProviderName : Intel
Date : 24/07/2022 00:00:00
Version : 20.70.32.1
Driver : oem12.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\netwtw6e.inf_amd64_ddded575f3a87757\netwtw
6e.inf
InBox : False
CatalogFile : Netwtw6e.cat
ClassName : net
ClassGuid : {4D36E972-E325-11CE-BFC1-08002BE10318}
ClassDescription : Network adapters
BootCritical : False
DriverSignature : Signed
ProviderName : Intel
Date : 17/01/2023 00:00:00
Version : 22.200.0.6
Driver : oem120.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\netwtw04.inf_amd64_e7569a918759c434\netwtw
04.inf
InBox : False
CatalogFile : Netwtw04.cat
ClassName : net
ClassGuid : {4D36E972-E325-11CE-BFC1-08002BE10318}
ClassDescription : Network adapters
BootCritical : False
DriverSignature : Signed
ProviderName : Intel
Date : 02/08/2022 00:00:00
Version : 19.51.42.2
Driver : oem17.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\newtek_audioportclass_multi.inf_amd64_abc4
1265aff31624\newtek_audioportclass_multi.inf
InBox : False
CatalogFile : NewTek_AudioPortClass_Multi.cat
ClassName : Media
ClassGuid : {4D36E96C-E325-11CE-BFC1-08002BE10318}
ClassDescription : Sound, video and game controllers
BootCritical : False
DriverSignature : Signed
ProviderName : NewTek Partners LLP
Date : 04/06/2022 00:00:00
Version : 1.0.2.14
Driver : oem19.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\u0388646.inf_amd64_cec79a959dad0433\u03886
46.inf
InBox : False
CatalogFile : U0388646.CAT
ClassName : Display
ClassGuid : {4D36E968-E325-11CE-BFC1-08002BE10318}
ClassDescription : Display adaptors
BootCritical : False
DriverSignature : Signed
ProviderName : Advanced Micro Devices, Inc.
Date : 17/02/2023 00:00:00
Version : 31.0.14033.1012
Driver : oem20.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\dtsapo4ultraasusextensionpkg.inf_amd64_96a
d9d48092ca7d8\dtsapo4ultraasusextensionpkg.inf
InBox : False
CatalogFile : dtsapo4ultraAsusextensionpkg.cat
ClassName : Extension
ClassGuid : {E2F84CE7-8EFA-411C-AA69-97454CA4CB57}
ClassDescription : Extensions
BootCritical : False
DriverSignature : Signed
ProviderName : DTS
Date : 08/06/2021 00:00:00
Version : 1.6.102.0
Driver : oem31.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\tbthostcontrollerextension.inf_amd64_ce999
21fed6ac464\tbthostcontrollerextension.inf
InBox : False
CatalogFile : TbtHostControllerExtension.cat
ClassName : Extension
ClassGuid : {E2F84CE7-8EFA-411C-AA69-97454CA4CB57}
ClassDescription : Extensions
BootCritical : False
DriverSignature : Signed
ProviderName : Intel(R) Corporation
Date : 13/07/2021 00:00:00
Version : 1.41.1193.0
Driver : oem5.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\e2fn.inf_amd64_19533fa54e0d0ffb\e2fn.inf
InBox : False
CatalogFile : e2fn.cat
ClassName : Net
ClassGuid : {4D36E972-E325-11CE-BFC1-08002BE10318}
ClassDescription : Network adapters
BootCritical : False
DriverSignature : Signed
ProviderName : Intel
Date : 21/09/2022 00:00:00
Version : 2.1.2.3
Driver : oem51.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\asusproart.inf_amd64_2f1dd0c6c0314622\asus
proart.inf
InBox : False
CatalogFile : asusproart.cat
ClassName : Extension
ClassGuid : {E2F84CE7-8EFA-411C-AA69-97454CA4CB57}
ClassDescription : Extensions
BootCritical : False
DriverSignature : Signed
ProviderName : ASUSTek Computer Inc.
Date : 31/03/2020 00:00:00
Version : 1.0.6.0
Driver : oem58.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\amdpcibridgeextension.inf_amd64_2b0b2bac86
a4cd1d\amdpcibridgeextension.inf
InBox : False
CatalogFile : amdpcibridgeextension.cat
ClassName : Extension
ClassGuid : {E2F84CE7-8EFA-411C-AA69-97454CA4CB57}
ClassDescription : Extensions
BootCritical : False
DriverSignature : Signed
ProviderName : AMD
Date : 28/06/2021 00:00:00
Version : 21.30.0.0
Driver : oem6.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\avolutess3ext.inf_amd64_19a80459690baf67\a
volutess3ext.inf
InBox : False
CatalogFile : AVoluteSS3Ext.cat
ClassName : Extension
ClassGuid : {E2F84CE7-8EFA-411C-AA69-97454CA4CB57}
ClassDescription : Extensions
BootCritical : False
DriverSignature : Signed
ProviderName : A-Volute
Date : 08/10/2021 00:00:00
Version : 1.3.15.0
Driver : oem61.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\extrtxusb_asus_avo_rtk.inf_amd64_9ea88b22f
0c8a3d8\extrtxusb_asus_avo_rtk.inf
InBox : False
CatalogFile : ExtRtXUsb.cat
ClassName : Extension
ClassGuid : {E2F84CE7-8EFA-411C-AA69-97454CA4CB57}
ClassDescription : Extensions
BootCritical : False
DriverSignature : Signed
ProviderName : Realtek
Date : 11/11/2021 00:00:00
Version : 1.0.0.54
Driver : oem65.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\atihdwt6.inf_amd64_e93648882ce41c80\atihdw
t6.inf
InBox : False
CatalogFile : AtihdWT6.cat
ClassName : MEDIA
ClassGuid : {4D36E96C-E325-11CE-BFC1-08002BE10318}
ClassDescription : Sound, video and game controllers
BootCritical : False
DriverSignature : Signed
ProviderName : Advanced Micro Devices
Date : 08/06/2022 00:00:00
Version : 10.0.1.24
Driver : oem71.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\pieextension.inf_amd64_fb20b53884701e14\pi
eextension.inf
InBox : False
CatalogFile : PieExtension.cat
ClassName : Extension
ClassGuid : {E2F84CE7-8EFA-411C-AA69-97454CA4CB57}
ClassDescription : Extensions
BootCritical : False
DriverSignature : Signed
ProviderName : Intel Corporation
Date : 19/07/2021 00:00:00
Version : 22.1070.2.1
Driver : oem74.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\e2fn.inf_amd64_d9445744f52b5b9b\e2fn.inf
InBox : False
CatalogFile : e2fn.cat
ClassName : Net
ClassGuid : {4D36E972-E325-11CE-BFC1-08002BE10318}
ClassDescription : Network adapters
BootCritical : False
DriverSignature : Signed
ProviderName : Intel
Date : 09/02/2023 00:00:00
Version : 2.1.3.3
Driver : oem78.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\netwtw08.inf_amd64_4ade3151b23d11d0\netwtw
08.inf
InBox : False
CatalogFile : Netwtw08.cat
ClassName : net
ClassGuid : {4D36E972-E325-11CE-BFC1-08002BE10318}
ClassDescription : Network adapters
BootCritical : False
DriverSignature : Signed
ProviderName : Intel
Date : 24/05/2022 00:00:00
Version : 22.150.0.3
Driver : oem86.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\avolutess3vad.inf_amd64_a869f777f74fb408\a
volutess3vad.inf
InBox : False
CatalogFile : AVoluteSS3Vad.cat
ClassName : MEDIA
ClassGuid : {4D36E96C-E325-11CE-BFC1-08002BE10318}
ClassDescription : Sound, video and game controllers
BootCritical : False
DriverSignature : Signed
ProviderName : Nahimic
Date : 07/06/2022 00:00:00
Version : 1.0.3.0
Driver : oem88.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\netwtw6e.inf_amd64_4d2bf8e0a2f591ce\netwtw
6e.inf
InBox : False
CatalogFile : Netwtw6e.cat
ClassName : net
ClassGuid : {4D36E972-E325-11CE-BFC1-08002BE10318}
ClassDescription : Network adapters
BootCritical : False
DriverSignature : Signed
ProviderName : Intel
Date : 23/11/2022 00:00:00
Version : 22.190.0.4
Driver : oem93.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\avolutess3vad.inf_amd64_79cd9525c9a5e12a\a
volutess3vad.inf
InBox : False
CatalogFile : AVoluteSS3Vad.cat
ClassName : MEDIA
ClassGuid : {4D36E96C-E325-11CE-BFC1-08002BE10318}
ClassDescription : Sound, video and game controllers
BootCritical : False
DriverSignature : Signed
ProviderName : Nahimic
Date : 14/10/2021 00:00:00
Version : 1.0.2.0
PS C:\WINDOWS\system32>
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
03-07-2023 05:24 AM
Hello, Murph_9000.
We appreciate you providing the pertinent information and will send it for verification to the appropriate department.
However, there is no 1.1.4.38 or 2.1.3.3 version of the Intel I225/I226 LAN driver for Windows 11 64-bit released for the ROG CROSSHAIR VIII EXTREME according to the official ASUS website.
The latest version is Version 2.1.2.3, which was released on December 20, 2022.
Could you kindly clarify which models of the motherboard you downloaded from the official support page have the problem you described above?
Or else, please provide the link from which you downloaded the driver and the model you tested with.
Also, may I ask what extraction tool you used to unzip the compressed driver file you downloaded?
If you aren't already using it, kindly test unzipping using 7-Zip and confirm if the result is still the same.
Thank you.
We appreciate you providing the pertinent information and will send it for verification to the appropriate department.
However, there is no 1.1.4.38 or 2.1.3.3 version of the Intel I225/I226 LAN driver for Windows 11 64-bit released for the ROG CROSSHAIR VIII EXTREME according to the official ASUS website.
The latest version is Version 2.1.2.3, which was released on December 20, 2022.
Could you kindly clarify which models of the motherboard you downloaded from the official support page have the problem you described above?
Or else, please provide the link from which you downloaded the driver and the model you tested with.
Also, may I ask what extraction tool you used to unzip the compressed driver file you downloaded?
If you aren't already using it, kindly test unzipping using 7-Zip and confirm if the result is still the same.
Thank you.
Due to the ongoing regional holidays, my responses may be slightly delayed.
Thank you in advance for your patience 🙂
Thank you in advance for your patience 🙂
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
03-07-2023 09:24 AM
I'm running the Crosshair VIII Extreme board, but grabbed the newer driver to take a look at it. I'm aware that it's not listed by ASUS for the X570 board, but it's the same Intel drivers for all I225/I226 interfaces. I downloaded it from https://dlcdnets.asus.com/pub/ASUS/mb/04LAN/DRV_LAN_Intel_I225_I226_TSD_W11_64_V11438_20230303R.zip?.... I'm well aware of the differences between X570 and X670.
I extracted the zip file using the extraction built in to Windows 11 File Explorer (right-click on ZIP file, Extract All). That's not relevant to what I'm reporting, as the file is small and clearly not corrupted. The contents of deloeminf.ps1 are the same regardless of the tool used to extract/view it, e.g. it's the same when extracted/viewed with WinRAR rather than the OS tools. The SHA256 hash of the deloeminf.ps1 that I have is FBDB6B9ED83AFAC787E08823BF3944F0BCB28D3138C469DFB784FB995F028A25, and the full contents are posted in the first CODE box at the top of this thread.
The problem will occur on any system where the supplied version of deloeminf.ps1 runs, both Intel and AMD, both current/latest platforms and older platforms. The impact will be larger on some systems than others, depending on the devices installed. The script will be harmful on any Windows 10/11 system, as it matches against "ClassGuid = {e2f84ce7-8efa-411c-aa69-97454ca4cb57}", which is the Microsoft GUID for "Extension" drivers; so it would delete a bunch of drivers which are part of the Realtek USB Audio driver packages, for example.
I extracted the zip file using the extraction built in to Windows 11 File Explorer (right-click on ZIP file, Extract All). That's not relevant to what I'm reporting, as the file is small and clearly not corrupted. The contents of deloeminf.ps1 are the same regardless of the tool used to extract/view it, e.g. it's the same when extracted/viewed with WinRAR rather than the OS tools. The SHA256 hash of the deloeminf.ps1 that I have is FBDB6B9ED83AFAC787E08823BF3944F0BCB28D3138C469DFB784FB995F028A25, and the full contents are posted in the first CODE box at the top of this thread.
The problem will occur on any system where the supplied version of deloeminf.ps1 runs, both Intel and AMD, both current/latest platforms and older platforms. The impact will be larger on some systems than others, depending on the devices installed. The script will be harmful on any Windows 10/11 system, as it matches against "ClassGuid = {e2f84ce7-8efa-411c-aa69-97454ca4cb57}", which is the Microsoft GUID for "Extension" drivers; so it would delete a bunch of drivers which are part of the Realtek USB Audio driver packages, for example.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
03-12-2023 08:06 PM
Hello, Murph_9000.
There will be differences in the content of the associated drivers for various motherboard models.
Please install the drivers released on the support page for the motherboard you are currently using.
Moreover, the concept indicates that the results of different extraction tools may have some differences, and the relevant team suggests unzipping the installation file with 7-Zip.
Therefore, it is recommended that you refer to the above advice and try again.
Thank you.
There will be differences in the content of the associated drivers for various motherboard models.
Please install the drivers released on the support page for the motherboard you are currently using.
Moreover, the concept indicates that the results of different extraction tools may have some differences, and the relevant team suggests unzipping the installation file with 7-Zip.
Therefore, it is recommended that you refer to the above advice and try again.
Thank you.
Due to the ongoing regional holidays, my responses may be slightly delayed.
Thank you in advance for your patience 🙂
Thank you in advance for your patience 🙂
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
03-13-2023 05:30 AM
The deloeminf.ps1 script is the same when extracted with 7-Zip. It will attempt to delete Realtek USB Audio drivers, AMD drivers, and many more. The bug exists regardless of the specific motherboard I am using. I do not have a problem with the I225-V on my motherboard, it runs just fine with both the 2.1.2.3 driver from the X570 Extreme and the 2.1.3.3 driver from the X670E Extreme (manually installed with Windows tools, instead of the ASUS installer). This is not a support request, it is a bug report. The bug is repeatable and demonstrable (see earlier post where I provided a diagnostic variant of the script which shows the long list of drivers it erroneously attempts to delete). A fix for the bug is provided below.
Original deloeminf.ps1 script from the March 3rd driver release:
The problem is the two pattern matches above, highlighted in red. Those match INF files which are completely unrelated to the Intel LAN driver. In particular, they match multiple drivers within the Realtek USB Audio driver package, several AMD drivers, and many more. The script will incorrectly attempt to delete drivers which it absolutely should not be touching. This will happen on any Windows 10/11 system, any motherboard, both Intel and AMD platforms.
"get-content $file | select-string -pattern 'e2f' -SimpleMatch" matches far more than just the Intel e2f LAN drivers. It matches many others which just happen to contain the "e2f" as part of a hexadecimal number (GUIDs, PCI/USB hardware IDs, registry values, etc).
Here is a minimally changed version of the script which has a very low chance of matching anything other than the intended drivers. This is a fix for the bug:
This also combines the two cases (e2f and e2f68) from the original script into one, and adds the e2fn case (which wasn't explicitly in the original, but was picked up by the e2f case). This modified script behaves as I believe the original script supplied in the March 3rd driver was intended to behave. It behaves like the OEMFILE.CMD implementation used in older driver releases. The only false positive which might occur with it is if some other vendor happens to name an unrelated driver e2f/e2f68/e2fn, which is possible but reasonably unlikely.
The installer scripts for the Intel LAN driver absolutely should not be touching unrelated drivers.
Original deloeminf.ps1 script from the March 3rd driver release:
$oemfiles = gci $ENV:windir\inf\oem*.inf
foreach($file in $oemfiles)
{
if (get-content $file | select-string -pattern 'e2f' -SimpleMatch)
{
.\devcon.exe dp_delete $file.name
}
elseif (get-content $file | select-string -pattern 'e2f68' -SimpleMatch)
{
.\devcon.exe dp_delete $file.name
}
}
The problem is the two pattern matches above, highlighted in red. Those match INF files which are completely unrelated to the Intel LAN driver. In particular, they match multiple drivers within the Realtek USB Audio driver package, several AMD drivers, and many more. The script will incorrectly attempt to delete drivers which it absolutely should not be touching. This will happen on any Windows 10/11 system, any motherboard, both Intel and AMD platforms.
"get-content $file | select-string -pattern 'e2f' -SimpleMatch" matches far more than just the Intel e2f LAN drivers. It matches many others which just happen to contain the "e2f" as part of a hexadecimal number (GUIDs, PCI/USB hardware IDs, registry values, etc).
Here is a minimally changed version of the script which has a very low chance of matching anything other than the intended drivers. This is a fix for the bug:
$oemfiles = gci $ENV:windir\inf\oem*.inf
foreach ($file in $oemfiles)
{
if (get-content $file | select-string -pattern 'CatalogFile\s*=\s*e2f(68|n)?.cat')
{
.\devcon.exe dp_delete $file.name
}
}
This also combines the two cases (e2f and e2f68) from the original script into one, and adds the e2fn case (which wasn't explicitly in the original, but was picked up by the e2f case). This modified script behaves as I believe the original script supplied in the March 3rd driver was intended to behave. It behaves like the OEMFILE.CMD implementation used in older driver releases. The only false positive which might occur with it is if some other vendor happens to name an unrelated driver e2f/e2f68/e2fn, which is possible but reasonably unlikely.
The installer scripts for the Intel LAN driver absolutely should not be touching unrelated drivers.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
03-13-2023 11:19 PM
Hello, Murph_9000.
I have provided your feedback to the relevant department for confirmation, and I am currently waiting for confirmation.
If there is a response or an information update, I will inform you as soon as possible in the comment.
Thank you.
I have provided your feedback to the relevant department for confirmation, and I am currently waiting for confirmation.
If there is a response or an information update, I will inform you as soon as possible in the comment.
Thank you.
Due to the ongoing regional holidays, my responses may be slightly delayed.
Thank you in advance for your patience 🙂
Thank you in advance for your patience 🙂
