Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Update your Win 7 installation media

3 Weeks Ago   #701
SIW2

Microsoft Community Contributor Award Recipient

Vista x64 / 7 X64
 
 

I hadn't previously changed the import code of 7updater to match the changes in updatepack command functions. Alerted to it by your test. Should be fixed in next version.

Quote:
I created the command you specified (calling it SetupChipset.cmd)
The file has to be named setupcomplete.cmd or it won't work.


My System SpecsSystem Spec
.
3 Weeks Ago   #702
SIW2

Microsoft Community Contributor Award Recipient

Vista x64 / 7 X64
 
 

My System SpecsSystem Spec
3 Weeks Ago   #703
SIW2

Microsoft Community Contributor Award Recipient

Vista x64 / 7 X64
 
 

I am contemplating adding a little menu to the bootable wim files

Update your Win 7 installation media-menu1.jpg


My System SpecsSystem Spec
.

3 Weeks Ago   #704
SIW2

Microsoft Community Contributor Award Recipient

Vista x64 / 7 X64
 
 

7UPv48 on first post.

If it is preferred without the above menu, delete menux64 and menux86 from the BIN folder.

Update your Win 7 installation media-binmenu.jpg


My System SpecsSystem Spec
3 Weeks Ago   #705
dsperber

Windows 7 Pro x64 (1), Win7 Pro X64 (2)
 
 

Quote   Quote: Originally Posted by SIW2 View Post
7UPv48 on first post.
Does this address the issue with \Imports not working?

If so, is there something unique to how 7UP places \Scripts into INSTALL.WIM that will work via 7UP, while not working via Integrate7?

As you may have seen from my post on this topic in the Integrate7 thread, I placed what I believed to be the proper items (including the correctly named SetupComplete.CMD) where they should be placed using Integrate7, and sure enough everything got copied to \Windows\Setup exactly as is supposed to happen using 7UP. And yet, the Intel Chipset INF Utility did not appear to get executed, because the three hardware items still showed as "other devices" in Device Manager. I had to manually run the utility myself post-install in order to correct this.

So, I ask again. Even if 7UPv48 now fixes \Imports, it seems that running of the SetupComplete.CMD is not occurring... at least with Integrate7. I hate to waste another hour running the new 7UP process only to discover once again that the Intel chipset utility is still not being invoked during the Win7 install.
My System SpecsSystem Spec
3 Weeks Ago   #706
SIW2

Microsoft Community Contributor Award Recipient

Vista x64 / 7 X64
 
 

7UPDATERv48 copies the contents of the IMPORT folder to the mounted install.wim image.

If there is an $OEM$ folder in dvd\sources, Windows setup.exe routine copies the $OEM$\$$ contents to %windir%.

Either

sources\$oem$\$$\Setup\Scripts\SetupComplete.cmd

OR

%windir%\setup\scripts\SetupComplete.cmd.
My System SpecsSystem Spec
3 Weeks Ago   #707
dsperber

Windows 7 Pro x64 (1), Win7 Pro X64 (2)
 
 

Quote   Quote: Originally Posted by SIW2 View Post
create folders inside it Windows\Setup\Scripts\chipset . Create setupcomplete.cmd in the Scripts folder

setupcomplete.cmd
Code:
@echo off
 IF EXIST %windir%\Setup\Scripts\chipset\Setupchipset.exe (
%windir%\Setup\Scripts\chipset\Setupchipset.exe -s -noreboot
 )
7UPDATER will copy the windows folder from IMPORT into the mounted wim.
First, I confirm that the latest 7UPv48 now does copy the \Windows\Setup folder found in \Import into INSTALL.WIM, which eventually is duplicated in the installed Win7, becoming \Windows\Setup. So this issue is now fixed.

However I still see the three "other device" items in Device Manager.



So it looks like either the SetupComplete.cmd isn't being run, or it is running but failing. Time for a test. Note that I simply created the cmd exactly as you prescribed.

So I decided to manually execute it, to see if it is coded properly and/or has some other issue the prevents it from accomplishing what I wanted.

So I reduced the cmd to simply "SetupChipset.exe -s -reboot" and invoked it with "run as administrator". And it opened up a command prompt window briefly which then closed. And no change in Device Manager.

I then tried just "SetupChipset.exe", and of course it launched. I canceled it.

I then tried "SetupChipset.exe /s", and this time it launched and started running quietly. Looks like /s might be the proper way to specify "silent mode". It ran for a few seconds and then presented a popup message with text complaining of an invalid signature, and did I want to run it anyway... so I said OK. This message doesn't occur when simply running the utility as a normally launched EXE, without the /s operand. I don't know why it should occur when /s is present.

Anyway, a few seconds later I got a second occurrence of the same popup message again complaining about the unauthorized signature. Once again I replied OK and it continued on.

And finally, a few seconds later, it completed. And when I looked in Device Manager now all three of those devices had vanished from "other devices". There were three devices originally, and I saw only two signature messages. Perhaps this relate to the two PCI devices, and the third SM device didn't trigger a signature issue. Don't know.

Bottom line: I'm speculating that the SetupComplete.CMD script actually did run, but failed... same as it does when I run it manually. This could be due to the -s operand instead of /s. But even when I use /s there now occurs two signature error messages requiring my OK to proceed, which do not occur when simply running the Intel utility externally as an EXE while Windows is up and operating.

It looks like this particular issue may simply not be appropriate for trying to get addressed automatically at Windows install by putting something in \Scripts. Not worth the fight. I will simply realize that the Intel chipset utility must be run after the Windows install is completed, as would be intuitively appropriate after reviewing Device Manager to look for problems, like this one.


I've already removed the five (of seven found by Windows Update after the install completes) "undesirable" MSU fixes I'd placed in \Hotfixes, as they are also deemed "undesirable" in the Integrate7 method.

And I will now remove the Intel Chipset INF Utility items from \Import, since it doesn't seem possible to get it to run totally silently and without some human intervention related to the signature issue, whatever is triggering it.

Otherwise, all the rest of my Z170 hardware and drivers is now completely addressed by how I've built both the 7UP and Intergrate7 tools. I think I finally have the completed Win7 install media from 7UP, both in bootable USB form as well as in ISO form (for use in Win7-VM). And furthermore, the bootable USB can be constructed to target either an MBR or GPT drive.
My System SpecsSystem Spec
.
3 Weeks Ago   #708
SIW2

Microsoft Community Contributor Award Recipient

Vista x64 / 7 X64
 
 

Quote:
dsperber
invalid signature
That might be the issue.

It can be run semi-automatically at first logon.

Pop a cmd file in the startup folder which points at wherever you put setupchipset.exe - for example on the root of the drive ( %systemdrive%\chipset\setupchipset.exe ) Something like this:

folder structure in IMPORT:

ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\MY.CMD

chipset\the extracted chipset zip file stuff in here

Update your Win 7 installation media-chipset-folder-contents.jpg

MY.cmd something like this:
Code:
@ECHO OFF
IF EXIST %SYSTEMDRIVE%\chipset\setupchipset.exe (
 echo running setupchipset
 Start /wait %SYSTEMDRIVE%\chipset\setupchipset.exe
 RD /s /q "%SYSTEMDRIVE%\chipset"
  )
  
DEL "%~f0"


My System SpecsSystem Spec
3 Weeks Ago   #709
SIW2

Microsoft Community Contributor Award Recipient

Vista x64 / 7 X64
 
 

Tested the above - it works fine.
My System SpecsSystem Spec
3 Weeks Ago   #710
dsperber

Windows 7 Pro x64 (1), Win7 Pro X64 (2)
 
 

Quote   Quote: Originally Posted by SIW2 View Post
Tested the above - it works fine.
What works fine... using this \Imports approach to place something into the Start Menu that self-initiates at first-logon post-install and then deletes itself?

Looks to me that your new MY.CMD no longer runs "silently", but simply is a novel way to not accidentally overlook the need to run the chipset utility to address the Device Manager issue. Results in an auto-launch of SetupChipset.exe automatically at first Windows login, using this revised method so that it 100% guarantees running immediately on the first login to the newly installed Windows and never again.

And thus it is also "in the foreground", meaning it is just like a normal manual double-click launching of the program which produces the standard Intel program window, NEXT buttons, etc., so that there should be no "invalid signature" issue as unexpectedly seemed to be the case for me when I tried to run it in "silent mode".

Furthermore, this new approach should also work with Integrate7, and its own \Add-these-files-to-Windows folder (identical in concept to your \Import).

If I'm willing to face the reality that this program must be run in the foreground, manually launched, and that this new idea of yours is a clever way to "assist so as not to overlook" and also to "force running it in the foreground at first opportunity", seems perfectly fine to me. I will test it out myself.

Cute.
My System SpecsSystem Spec
Reply

 Update your Win 7 installation media




Thread Tools




Similar help and support threads
Thread Forum
TEST -Update 7 installation media
Anyone who wants to give this a try: 1. Put your win7 dvd in the drive, rt click it and select COPY. Then rt click your partition (e.g. C ) and PASTE. It will take a few mins and you should have afolder on c containing the installation files, like this: 2. Install WUD - tiny program:
Installation & Setup
Windows Media Player will not update media library
I am a music downloader. It used to be that WMP12 would update the mp3 music folders to where the folder contents would read as follows: 01 'Track Name' 02 'Track Name' 03 'Track Name' and so on... This is no longer the case. WMP will not update my media library files, although it...
General Discussion
How to get installation media?
Hi, I've got an HP Pavilion laptop that came with Windows 7 installed as a Vista upgrade. I'd like to blow it away, repartition the disk for dual boot with Linux, and do a clean install of Windows 7. The only problem (I think) is that I don't have the installation media. I've searched online...
Installation & Setup
Bad installation media I think
Remember me? I'm the one with the pirated W7 Ultimate. I finally bought a genuine W7 Ultimate disk from Newegg for the tune of $310. Still working with MasterCard to get my money back. It looks favorable. When I went to do a clean install the auto-boot worked but it hung up with a blue screen...
Installation & Setup
media smart server update corrupted media center
I have 4 computers all running windows 7-3 in 32 and 1 in 64. All were working fine and no issues with my mediasmart 470 server. I only have one computer with console running. The other day pp3 came out and has made a mess of my computer that has connector to server. It seems to have corrupted...
Media Center


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 07:07.
Twitter Facebook