Error Invalid Command Line 1639
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Tue, 11 Oct 2016 20:08:08 GMT by s_wx1094 (squid/3.5.20)
från GoogleLogga inDolda fältSök efter grupper eller meddelanden
Popular Forums Computer Help Computer Newbies Laptops Phones TVs & Home Theaters Networking & Wireless Windows 7 Windows 10 Cameras All Forums News Top Categories Apple Computers https://www.cnet.com/forums/discussions/help-i-got-this-error-1639-291173/ Crave Deals Google Internet Microsoft Mobile Photography Security Sci-Tech Tech Culture Tech http://www.pcreview.co.uk/threads/error-1639-invalid-command-line-argument.1544290/ Industry Photo Galleries Video Forums Video Top Categories Apple Byte Carfection CNET Top 5 CNET Update Googlicious How To Netpicks Next Big Thing News On Cars Phones Prizefight Tablets Tomorrow Daily CNET Podcasts How To Top Categories Appliances Computers Gaming Home Entertainment Internet Mobile Apps Phones Photography Security windows installer Smart Home Tablets Wearable Tech Forums Speed Test Smart Home Top Categories Tour CNET Smart Home Smart Home News Smart Home How To Best Smart Home Devices Cars Top Categories Car Reviews Best Cars New Cars Used Cars Deals Top Categories Cheapskate Best Tech Under $50 All Deals Tech Deals Non-Tech Deals Audio Deals Cell Phone Deals Desktop Deals Laptop invalid command line Deals Hard Drive & Storage Deals Printer Deals Tablet Deals Camera Deals Monitor Deals Software Deals TV Deals Web Hosting VPN Services WordPress Hosting Domain Names Download Sign In / Join Sign In to CNET Join CNET Member Benefits My Profile Forums Sign Out US Other editions United Kingdom Australia China France Germany Japan Korea CNET en Español CNET Forums Windows Legacy OS [Help] i got this error :-1639 Windows Legacy OS forum About This ForumCNET's Forum on Windows legacy operating systems, (XP, 2000/NT, ME, & Windows 95/98) is the best source for finding help or getting troubleshooting advice from a community of experts. Discussions cover Windows 2003 Server, Windows installation, adding and removing programs, driver problems, crashes, upgrading, and other OS-related questions.Real-Time ActivityMy Tracked DiscussionsFAQsPoliciesModerators General discussion [Help] i got this error :-1639 by Gzim-Berisha / April 11, 2008 8:57 AM PDT on some pograms when i try to install them, this error ocurs just before the instalation, error 1639 "Invalid command line argument. Consult the Windows Installer SDK for detailed command line help."I`m using windows XP sp2
OS: Windows 2000 MSI version: 2.00.26.1183 (also given as 2.0.2600.1183) All of a sudden Installer is failing with error 1639 -- invalid command line argument. This is on installation packages from Microsoft, whether automated, i.e. clicking on some selfextrcting, self-installing archive, or by invocation on the command line. The registry entries appear to be correct, i.e. install is: "C:\WINNT\system32\msiexec.exe" /i "%1" %* and repair, uninstall and patch have the correct command line arguments /f, /x, and /p respectively Invocation on the command line allows logging. It does appear that there are no command line arguments passed to the log even though MSI parses the command line and complains if the arguments are incorrect/inappropriate. I can provide the log file if someone is interested. I have found only a few posts or web sites with installer and error 1639. Any suggestions would be much appreciated. Gerard Gerard Tromp, Oct 22, 2003 #1 Advertisements Kallely Sajan Guest Check if System and user installing the kit have full permissions on C:\, C:\WINNT\system32, C:\WINNT, C:\WINNT\Installer, and %TEMP% -- Regards, Sajan. PS: Please don't send me direct emails, use the newsroom. "Gerard Tromp" <> wrote in message news:%... > Greetings! > > OS: Windows 2000 > MSI version: 2.00.26.1183 (also given as 2.0.2600.1183) > > All of a sudden Installer is failing with error 1639 -- invalid command line > argument. This is on installation packages from Microsoft, whether > automated, i.e. clicking on some selfextrcting, self-installing archive, or > by invocation on the command line. > > The registry entries appear to be correct, i.e. install is: > "C:\WINNT\system32\msiexec.exe" /i "%1" %* > and repair, uninstall and patch have the correct command line arguments /f, > /x, and /p respectively > > Invocation on the command line allows logging. It does appear that there are > no command line arguments passed to the log even though MSI parses the > command line and complains if the arguments are incorrect/inappropriate. > > I can provide the log file if someone is interested. > > I have found only a few posts or w