We've downloaded the latest Intel WiDi drivers (3.1.29) for our Lenovo T430 and X230 laptops. All the other drivers for the devices work fine apart from the WiDi driver. We install all of the other drivers before the WiDi one and reboot to ensure it has all of it's prerequisites, and it still doesn't work. For info, Wifi driver we're using is Intel PROSet Wireless 15.2 and WiDi is supporting on these models of laptop.

 

Using setup.exe /?, you can see that the recommended command line is setup.exe /s /v/qn. Every time you run this you get a return code of 1603, which doesn't tell us much...

I've tried just running setup.exe /s and setup.exe /s /v/qb to view progress, but that gives the same result. I've also tried using the extracted MSI from within the temp directory and using that with msiexec /i "Intel(R) WiDi.msi" /qb, but that doesn't work either (again, 1603 error).

 

Here is the log file from the install: Microsoft SkyDrive - Access files anywhere. Create docs with free Office Web Apps.

 

Installing it manually does work fine, but we need to script it as we are deploying it to thousands of clients. Has anyone come across this and solved it? We're installing on clean Windows images by the way

 

TIA.

1 Comment   [ + ] Show Comment

Comments

  • We're trying to use SCCM 2012 to deploy the Intel WiDi 6.0.60.0 to Dell 7710s and get the same results. WiDi will install when the user is logged on (silently or not) but won't install when they are not. Having the task sequence run as a user doesn't work either. One has to actually be logged in. We get incompatible h/w (can't be if manual install works) or sometimes get error that newer version of software is already installed (no WiDi installed yet). There must be some internal modules that can't handle running with System or simulated account. WiDi 6.0.52.0 WILL install but it doesn't work with this new model PC. Only 6.0.60.0 will work. So for now we're deploying after the build.
Please log in to comment

Answers

0

Have you tried granting the system account full acces to the destination folder? 1603 errors aren't necessarily generic and are many times occured when  the system account t is used to install to a destination where it doesn't have sufficient rights. 

Answered 11/29/2012 by: jdornan
Red Belt

Please log in to comment
0

I finally got this working during image deployment in SCCM 2012 R2 using the command line provided by HP here: ftp://g4u0180.houston.hp.com/ftp4/pub/softpaq/sp74001-74500/sp74021.cva

 

"Setup.exe" GFX=F /S /v"/qn WIDIAPP_DESKTOP_SHORTCUT=0 DISABLE_IWD_UPDATES=1 /log C:\temp\Intel_WiDi.log"

Answered 03/08/2016 by: danwclark
White Belt

Please log in to comment
0
Hi,

With Latest WiDi version "allow users to interact with this programm" and instalation goes fine .... Without this parametter instalation fails with 1603.
Answered 01/17/2015 by: rukicc
White Belt

Please log in to comment
0
This is not going to be a five minute fix, but lets look at the evidence.
1. It installs manually OK - this presumes you are using the full UI and not manually running the silent install.
2. You are getting the platform not supported error - dangerous to assume that it is a generic message until you have conclusive proof.

So what do I see - a silent install fails and a manual full UI install works. What is the difference?  The InstallUI sequence does not run on a silent install.  Obvious first point of diagnosis is to run VERBOSE logs of both a silent install and a manual install and check public property values set during the InstallUI sequence. It may well be that a public property is set during the InstallUI Sequence that is required for the InstallExecute sequence to complete successfully. Maybe the platform check takes place in the UI sequence only, in  which case adding the check to the Execute sequence would be a logical resolution, or even hard coding the property value via a transform.

If that is not the issue then comparing the silent and full UI logs is really the best way forward in finding the actual cause.
Answered 01/20/2015 by: EdT
Red Belt

Please log in to comment
0

This Platform is not Compatible for the Intel WiDi Communication Manager installation to proceed 

 

apparently your hardware does not support Widi?

 

 

Answered 11/21/2012 by: jaybee96
Red Belt

  • check Lenovo why this occurs?
  • are you sure you are using the latest drivers..
    http://support.lenovo.com/en_US/research/hints-or-tips/detail.page?&DocID=HT073834
  • As I stated in my initial post... "Installing it manually does work fine". I can run the MSI manually and it will install perfectly, it is only scripting it with MSIEXEC that does not work.

    Again, I have the latest Lenovo drivers and my device IS supported as it shipped with it in the OEM image.

    The "platform not compatible" error is just a generic message that it spits out when it can't install I reckon. My command line is msiexec /i "Intel(R) WiDi.msi" /qn. I've tried renaming the MSI, using /qb and all sorts, nothing worked.
Please log in to comment
Answer this question or Comment on this question for clarity