The UAC was the cause of it most likely. It is for the best to keep UAC disabled for the installation process and activate it again after its done. @CaptainSpeleo I noticed that you refer to kb2763674 as SHA256 Support. This is a bit inaccurate and might confuse someone. This update just fixes a bug related to SHA256. Doesn't add SHA256 support. Also SHA2 and SHA256 is the same thing as far as I understand. Post 56 is now updated. I removed the registry file related to TLS1.1&1.2. The script that installs the cumulative will now add the registry file directly as part of the script without the need for an external reg file..
xrononautis: I changed the name in step #9 to "SHA-256 Bug Fix". Are you referring to this IE9 cumulative script that no longer needs the TLS registry file? MKDIR "%~dp0\tmp" FOR /F "usebackq delims=|" %%F IN (`dir /b "%~dp0" ^| findstr /i windows6.0-kb5022835-x64`) DO COPY %%F "%~dp0\tmp" CD "%~dp0\tmp" EXPAND -f:*windows6.0-kb*.cab *.msu "%~dp0\tmp" EXPAND -f:* *.cab "%~dp0\tmp" FOR /F "usebackq delims=|" %%F IN (`dir /b "%~dp0\tmp" ^| findstr /i package_2 ^| findstr /i .mum`) DO START /WAIT PKGMGR /ip /m:%%F /quiet /norestart FOR /F "usebackq delims=|" %%F IN (`dir /b "%~dp0\tmp" ^| findstr /i package_3 ^| findstr /i .mum`) DO START /WAIT PKGMGR /ip /m:%%F /quiet /norestart CD %HOMEDRIVE%\ %HOMEDRIVE% RMDIR /S /Q "%~dp0\tmp" It's the one that I'm currently using with the guide.
Thank you for the correction. Look at post 56 please. It is basically the same as this script but it has an extra registry section inside the batch file.
xrononautis: Just to make sure I understand you correctly, I should copy the ENTIRE text in post #724, (beginning with @echo off at the top and ending with exit at the bottom) into a Notepad text document and then give it name and a .bat extension? I then place that .bat file and the KB5022835 IE9 update into a folder and then run the .bat file and then reboot the computer? Doing this will install the KB5022835 IE9 update and will add TLS 1.1_TLS 1.2 support all at the same time?
May I know how you deployed the Vista to your 4th and 6th Intel computers ? After sysprep I built a WIM file replaced it in Sources folder , then save as a new ISO file In my HP820G1 , I change it to Legacy Boot Only with MBR partition and all goes well (need a Key to install ) also I could deploy it with a PE or another way ~~~ Not sure about 6th but the 4th can running only with Legacy Boot The reason your got a "Press any key to boot from CD or DVD" message is that maybe you forget to Disabled secure Boot
All of my 3rd/4th/6th generation Intel desktops and laptops have their BIOS set to legacy MBR mode because that's what I prefer to use. The "Press any key to boot from CD or DVD" message always appears when I boot with a bootable install disc, regardless of whether it's Windows Vista or 7 or 10. I researched this before I posted here, and I discovered that Windows Vista was never developed to support 4th generation Intel or newer computers. I have no desire to make a federal case out of this, but I do appreciate the feedback and advice.
frankielong: The support sites for my: Dell Precision M6800 Mobile WorkStation HP ZBook 17 G2 Mobile WorkStation (both are 4th generation 17.3" laptops) do not have drivers for Windows Vista, but they do have drivers for Windows XP and 7 and 10. That is another indication they do not support the install and use of Windows Vista. xrononautis: Did you see my reply in post #726?
Just checked my ivy bridge drivers, as I guessed the drivers are artificially blocked on Vista, as usual for Intel Code: ; Driver information ; [Manufacturer] %Intel% = IntelGfx, NTamd64.5.1, NTamd64.6.0, NTamd64.6.1, NTamd64.6.2, NTamd64.6.3, NTamd64.10.0 [IntelGfx.NTamd64.5.1] ; no install on XP [IntelGfx.NTamd64.6.0] ; no install on Vista ;===================================================================== ; Windows 7 Install ;===================================================================== [IntelGfx.NTamd64.6.1] %iIVBGD0% = iIVBD_w7, PCI\VEN_8086&DEV_0162 %iIVBGM0% = iIVBM_w7, PCI\VEN_8086&DEV_0166 %iIVBGD0GT1% = iIVBD_w7, PCI\VEN_8086&DEV_0152 %iIVBGM0GT1% = iIVBM_w7, PCI\VEN_8086&DEV_0156 ; IVB Server %iIVBGD0SRV% = iIVBD_w7, PCI\VEN_8086&DEV_016A %iIVBGD0SRVGT1% = iIVBD_w7, PCI\VEN_8086&DEV_015A %iVLVGMT0% = iVLV2M_w7, PCI\VEN_8086&DEV_0F31 Just replace the "no install on vista" with the W7 section. (if doesn't work, do the same with the XP drivers, in that case you get no aero, but better than nothing) Then, obviously, given you break the signature, you have to enable the test mode, or disable the signature enforcement manually at boot, to allow the installation of the drivers (on AMD64, step not needed on x86)
CaptainSpeleo : we're talking about the installation , not the drivers ~~~ even the original ISO file can be installed in 4th laptops without any integrated drivers
xrononautis: My questions in post #726 (above in quotes) have to do with a clean install of Windows Vista SP2 64-bit where no updates have yet been installed. They do not have to do with a clean install that has already been done and brought up to date. I am aware of your TLS .reg file in post #725 and have used it several times. You made me aware of it a long time ago. I actually deploy it before running the .bat file with the IE9 cumulative update.
If you include or no the Code: @echo off and "exit" in the script is not important. You can skip them if you prefer. The functionality of echo off is that you won't see the whole script being processed but rather only the results. The exit part I guess has no real value if it is placed at the end but it won't heart either. The only value that I can think of is that it makes it easier for people to figure out where the script starts and where it ends. Other than that is just for visual appeal as far as I understand.
Okay, thanks. I will test that IE9 update script when I do my next clean install. I just finished adding DAZ 2.2.2 loader to my Vista install media so it can automatically activate. I also want to test that to make sure I did it correctly and it works okay.
xrononautis: I just finished doing another clean install and update of Windows Vista Business SP2 64-bit. Everything went fine until I got to the point of deploying your long .BAT script that we discussed earlier. That script appeared to be working fine until it displayed an "Invalid Syntax" message and requested to delete a registry entry. After the script closed and I rebooted and then checked the IE9 version, I confirmed the version had not updated and TLS 1.1_1.2 had not been installed. I reverted back to my previous successful method of using the TLS 1.1_1.2 .REG file and then using the 10-line .BAT file. Everything worked fine and TLS 1.1_1.2 was added and IE9 updated to version 9.0.285. My newly-updated guide now has 4 parts in step #18. It may take longer to do, but it is what works for me, so I am going to leave it that way in the guide.
Hello Captain! That was entirely my fault. The line breaks where all over the place... no idea why or how did that happened. I fixed it now in Post #56. Please edit your post #724 as well so that people don't try to run this mess... I also realized that kb4056564 is not necessarily adding TLS 1.1 1.2 support. It has to do with something similar but in M$ support page about this update, TLS is not even mentioned. I was able to tick those boxes with just IE9 installed. Not sure though what is happening under the hood. Regarding the registry key it doesn't add support per say but it rather removes the OS Version check which is preventing you from using it other wise.