Jeronimo

Integration failed for (almost) all hotfixes. A lot of errormessages during integeration all refering to ...\hptemp??\DrUpdate.dll or ...\hptemp??\XmlLite.dll. Will test again as the vLite suggested, however earliest opportunity will be after the weekend. Just wanted to make note of it.

Install drivers on current system by use of setup. Afterwards open explorer for "Windows\inf" and check the most recent oem*.inf files. Those files can be opened in notepad and in the head it will show the original name. Copy that file from the appropriate Vista (x64/x86) folder along with the cat-file.

Without kb932596 all goes well. Just that I do not dare install kb941649 and also kb890830 can not be integrated yet (it also keeps appearing in Windows update when running it was run manually).

I will do a test with kb932596 excluded

I forgot this issue with kb932596 and integrated all updates. Now I also have some updates failing to install (beside KB941649): KB905866 (V12), KB939653 and KB941202. Is there going to be a fix for this or a new release anytime soon?

One of the greatest tweaks I have seen. To make Windows folders stick as in XP (instead of Ms. "I know better" Vista): [-HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\BagMRU] [HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\BagMRU] [-HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags] [HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags\AllFolders\Shell] "FolderType"="NotSpecified"

Similar issues here. My system did not boot at all, not normally, not in safe mode and not after selecting Last good configuration. I had a test installation of Vista (x64) from which I created a new installation with vLite. This installation also hung at the final step of the installation process. Fortunately I had only installed 2 of patches (along with nHancer, Nvidia graphics tweaking tool) and my guess was the update mentioned here was the cause. After keeping it out of the integration of updates, installation went fine. I am staying clear from this update, until the cause and a solution have been found.

Partly works for Vista x64. Renaming new folders is resolved. Renaming a "specific" existing folder or even moving them fails even after taking ownership and correcting rights: INGEBOUWD\Administrators:F INGEBOUWD\Administrators:(OI)(CI)(IO)F NT AUTHORITY\SYSTEEM:F NT AUTHORITY\SYSTEEM:(OI)(CI)(IO)F INGEBOUWD\Gebruikers:(OI)(CI)F NT AUTHORITY\Geverifieerde gebruikers:(OI)(CI)F

DirectX Web Installer does not give an error anymore, however it also does not download anything (issue youw ere having as well). Need to check further to make sure, but it looks good indeed. thanks for putting the effort in this.

Nuhi, any luck with the DirectX Web installer issue?

I would vote for the 2nd, however I fear for the first. I doubt the Setup would continue/finish without an internet connection. Only thing I can come up with is that it is a localisation that required update (and you are using English? Or Croatian?).

After accepting the license it should check on the internet for updates (eror when not connected) and reportn those after which you can continue installing. After it has performed those action you should be able to select finish. I do not understand, why you do not get to see any directx updates. For some benchmarks an SDK-part is needed (d3d_33.dll?) before you can run it. I think it was this techdemo for DirectX 10 that required some additional files for DirectX before it could run.

Sure, no problem. I only changed the location under the driver-section (privacy reason).

It can only be run once, after that the update it installed and will not make connection again. If you run it on a clean Windows with and without IE removed by vLite, then it will only work when IE is still present. IF IE is removed , you will get an errormessage and no possibility to continue and download/install DirectX. Some parts of DirectX 9 are not present under Vista and for this you need to perform an additional installation.

If something does not work that is supposed to work, then it is a bug. If you state it is a dependancy issue, then maybe include (fix) it as such. I can understand you do not want to investigate just because 1 user has issues with it and you can spend your time on something else helping more users. Still it should be solved (1 way or the other) in my opinion. I do not know how to explain better.

Well first the Redist pack is way bigger than what the DirectX web setup downlaods and secondly if there is 1 problem, there could be more. I would not like other programs having such issues and this could be the case. Because it is a program from Microsoft that does not work, it troubles me even more. Point is: if I keep IE with vLite and install Vista then dxwebwetup works. If IE is removed, then it does not.

I spend another 2 to 3 houts investigating with Process Monitor, but no luck. It should after accepting the license show which files will need to be downloaded, but it only gives the error. Hope you have more success. Here again the error from DirectX.log: 07/07/07 19:40:38: DXWSetup: ***** DXWSETUP ***** 07/07/07 19:40:38: DXWSetup: WinMain() 07/07/07 19:40:38: DXWSetup: IsIA64(): not IA64. 07/07/07 19:40:38: DXWSetup: Unable to get Version on target file E:\Windows\system32\directx\websetup\dsetup.dll 07/07/07 19:40:38: DXWSetup: Installed file E:\Windows\system32\directx\websetup\dsetup.dll 07/07/07 19:40:38: DXWSetup: Unable to get Version on target file E:\Windows\system32\directx\websetup\dsetup32.dll 07/07/07 19:40:38: DXWSetup: Installed file E:\Windows\system32\directx\websetup\dsetup32.dll 07/07/07 19:40:38: DXWSetup: GetDXVersion(): Unable to get RC string from registry. 07/07/07 19:40:38: DXWSetup: DirectX Version: 4.09.00.0904.00 07/07/07 19:40:38: DXWSetup: Setup Version: 4.09.00.0904.00 07/07/07 19:40:38: DXWSetup: A newer version of DirectX have been installed already. 07/07/07 19:40:38: dsetup32: IsWow64(): running on Wow64. ->07/07/07 19:40:41: DXWSetup: CDXWSetup::CDXWSetup() 07/07/07 19:40:41: DXWSetup: CDXWSetup::CDXWSetup(): CoCreateInstance() failed, error = 0x80040154. 07/07/07 19:40:41: DXWSetup: CDXWSetup::DownloadDXUpdate() 07/07/07 19:40:41: DXWSetup: CDXWSetup::DownloadDXUpdate(): CoCreateInstance() failed, error = 0x80040154. 07/07/07 19:40:41: DXWSetup: PreinstDlgProc(): CDXWSetup::DownloadDXUpdate() failed. 07/07/07 19:40:41: DXWSetup: WM_APP_ENDDOWNLOAD When it goes properly: 07/07/07 20:16:17: DXWSetup: CDXWSetup::CDXWSetup() 07/07/07 20:16:17: DXWSetup: CDXWSetup::DownloadDXUpdate() 07/07/07 20:16:17: DXWSetup: OnEngineStatusChange(): EngineStatus = 0x1, SubStatus = 0x0 07/07/07 20:16:17: DXWSetup: OnEngineStatusChange(): EngineStatus = 0x3, SubStatus = 0x0 07/07/07 20:16:17: DXWSetup: OnEngineStatusChange(): EngineStatus = 0x2, SubStatus = 0x0 07/07/07 20:16:17: DXWSetup: OnStartInstall(): DLSize = 81, InstallSize = 0 07/07/07 20:16:17: DXWSetup: OnStartComponent(): ID = DXUpdate, DLSize = 81, InstallSize = 0, str = DirectX 9.0 setup 07/07/07 20:16:17: DXWSetup: OnComponentProgress(): Phase = 0, Progress = 0 And the from DXerror.log: [07/07/07 19:40:41] module: DXWSetup(Jun 20 2007), file: dxwsetup.cpp, line: 65, function: CDXWSetup::CDXWSetup Failed API: CoCreateInstance() Error: (0x80040154) - Klasse is niet geregistreerd -------------------- [07/07/07 19:40:41] module: DXWSetup(Jun 20 2007), file: dxupdate.cpp, line: 431, function: CDXWSetup::DownloadDXUpdate Failed API: CoCreateInstance() Error: (0x80040154) - Klasse is niet geregistreerd -------------------- [07/07/07 19:40:41] module: DXWSetup(Jun 20 2007), file: psheets.cpp, line: 447, function: PreinstDlgProc CDXWSetup::DownloadDXUpdate() failed.

There are 2 ways: downloading AND running the application (restart firefox) or download and run another program, that provides you with a short key to enter on the site.

Well probable you will need to check it

As with previous release(s) DirectX Web Setup does not work when removing IE with vLite. Gives an errormessage right after accepting the license. Current version of DirectX Web Setup does also gives an error upon downloading,but this is not related to vLite according to me (previous version of the tool did wotk when IE was kept).

That Public folder is indeed annoying, however I think you need to registry settings for removal: Windows Registry Editor Version 5.00 ; Remove Public folder from Explorer [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer\Desktop\NameSpace\{4336a54d-038b-4685-ab02-99bb52d3fb8b}] [-HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\Desktop\NameSpace\{4336a54d-038b-4685-ab02-99bb52d3fb8b}]

Same issue occurs with Media Plyer Classic. I use Adaptive option under Power Settings to make it less anoying/frequent.

Not sure which folder it is, but maybe possible to check it as a protected file in vLite. Would definetely test this first, before doing a reïnstall, maybe after that another file is prompted as missing.

Removing Application Experience also drop use for update 932246 - March 2007 Windows Vista Application Compatibility Update. If you make use of an appliation as stated there and encounter issues, then Application Experience is best kept.

I checked a few 100 files, but no luck so far. ProgramFiles and ProgramFiles (x86) have only difference in IE folder and 1 "vgx"-file in the Common files. Furthermore in Windows folder a few differences in inf\IEM for instance, Offline Web Pages. I checked all files in base System32 and SysWOW64, there are more differences in amount of files there (subfolders) then there are the 5904 folders in Winsxs which I did not check. I think you have more and better methods to investigate. I might do 1 testrun if someone else does not test Application Experience. But this is not of real importance to me. I think I will have to settle with keep IE completely for now. Also my Virusscanner Avast prompts for a restart upon every boot, since the auto-update 4.7.997 -> 4.7.1001. Normally it just prompted for this once. Maybe it is related to IE as well, as I have had several other auto-updates from Avast that went without any issues. No unusual entries for Avast for what I can see with Autoruns or msconfig.