Jump to content
View in the app

A better way to browse. Learn more.

WinCert.net Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Solved] (Urgent) Intel chipset drivers not integratable by Win Toolkit for x86 versions of win 7

Featured Replies

Posted

Sorry Lego for naming this way the topic, but really, it's urgent because only tommorow I'll have the hardware available that will allow me to test this works. I have a friend with an Ivy-Bridge-Intel-based notebook, so the latest integratable Intel drivers aren't good / new enough for him.

 

It's my fault it's urgent because I forgot to ask you this earlier... I even forgot about a thread I opened at station-drivers :(

 

 

Long story short, newer Intel chipset drivers aren't recognised by Win Toolkit because of how they're named inside the infs. You can download them from here or here.

 

Until now, this is how a ''normal inf data'' helped Win Toolkit integrate them:

 

 

 

[Manufacturer]
%INTEL%=INTEL_SYS,NT.5.1,NTamd64

 

So NT5.1 for x86, But now...

 

 

%INTEL%=INTEL,NTamd64

 

So INTEL now stands also for x86, and Win Toolkit wrongfully ''thinks'' that driver is for x64 only. Or maybe it's a bigger picture here, and it's the same thing that DISM ''thinks''?

 

 

Please Lego make them integratable via WinToolkit, and this means AIO, the Driver Installer Tool and also the RunOnce tool (that scans for a ''drivers'' named folder in the install media).

 

I know it's much to ask, I know it's not your fault (Intel engineers seem to drink too much on the job these days), but please make a beta build asap. So I'll be able tommorow to also test the stuff that made me play with the infs and that made me start that thread at station-drivers.

  • Author

No longer an urgency. Talked my frind into coming next month again, so going to test this then.

 

But in the meantime I hope this will be implemented :D

  • 2 weeks later...
  • Author

Yes Lego, please solve this one soon :)

 

In a week from now I'll have again that hardware (on 15th of february), so it's again becoming urgent / please solve it by then :)this one is linked ;)

  • 3 weeks later...
  • 1 month later...
  • Author

Yep, can confirm this was fixed some builds ago. So please move it to the solved folder.

 

I  have another driver related bug, but I'll make another thread for it, as I also want to recheck it with the latest beta :)

  • Author

Tested in the latest beta, and still there are problems. It looks more like an interface minor issue, but I can'd say for sure.

 

See attached. The drivers are these - 9.4.4.1006. So don't ''solve'' this thread before investigating this :)

 

LE: Looks like a general adding drivers in AIO, ALL the drivers get that warning :( x86 windows 7 environment (host), x86 win 7 target iso, win 7 x86 drivers. 1.4.38.5 beta and also 1.4.37.20 gives this error.

post-25565-0-39674800-1396731504_thumb.p

Edited by RicaNeaga

  • 3 weeks later...

Please sign in to comment

You will be able to leave a comment after signing in

Sign In Now

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.