MagicAndre1981 Posted July 6, 2007 Share Posted July 6, 2007 (edited) Hi nuhi,I got the error with my DVD made with vLite 1.0 RC when I try to install or uninstall a Windows component through Control Panel in Vista.Here is the error message from Problem Reports and Solutions:Problem signatureProblem Event Name: WINDOWS_WCP_OTHER_FAILURE2OsVersion: 6.0.6000File: base\wcp\sil\merged\ntu\ntsystem.cppFunction: Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFileLine: 1461Status: c0000034Betriebsystemversion: 6.0.6000.2.0.0.256.1Gebietsschema-ID: 1031Here is my INI-file:; vLite preset file[Information]Version = 1.0 RC on 2.0.50727.879 Microsoft Windows NT 5.1.2600 Service Pack 2Target = Windows Vista ULTIMATE 32bit [Compatibility]ACDSee / XnViewKMPlayerPaint.NETAero GlasInternet ExplorerWindows SAT[Components];# Dienste #Distributed Link Tracking ClientMicrosoft DFS AbgleichRemote-RegistrierungVolume-SchattenkopieWindows Remote Management;# Hardware Unterstützung #FaxunterstützungInternet Small Computer System Interface (iSCSI)Smartcards;# Multimedia #Movie und DVD MakerSideShow;# Netzwerk #Mit Netzwerkprojektor verbindenMSN InstallerWindows Teamarbeit;# Sprachen #JapanischKoreanischTraditionelles ChinesischVereinfachtes Chinesisch;# System #JugendfreigabeNatürliche SpracheSicherheitscenterSynchronisierungscenterSystemwiederherstellungTablet PCTool zum Entfernen bösartiger SoftwareWindows BackupWindows DefenderZIP-Ordner;# Treiber #Drucker-ApolloDrucker-BrotherDrucker-CanonDrucker-CitizenDrucker-DellDrucker-DiconixDrucker-EpsonDrucker-Fuji XeroxDrucker-FujitsuDrucker-GenericDrucker-GestetnerDrucker-HPDrucker-IBMDrucker-InfotecDrucker-KonicaDrucker-Konica MinoltaDrucker-Kyocera MitaDrucker-LanierDrucker-LexmarkDrucker-MinoltaDrucker-Minolta-QMSDrucker-NECDrucker-NRGDrucker-OceDrucker-OkiDrucker-OkidataDrucker-OlivettiDrucker-PanasonicDrucker-QMSDrucker-RicohDrucker-SamsungDrucker-SavinDrucker-SeikoshaDrucker-SharpDrucker-SonyDrucker-StarDrucker-TallyDrucker-TektronixDrucker-Wipro ePeripheralsDrucker-XeroxScanner;# Zubehör #EingabehilfenMobility CenterSnipping ToolSprachunterstützung[Options]Speichervoraussetzung = 256MB[Protection][Drivers][Unattended]SpecRegionalAcceptEULASkipProductKeySkipAutoActivationNetworkLoc = 1ProtectPC = 2Any ideas what causes this issue?André Edited July 16, 2007 by MagicAndre1981 Link to comment Share on other sites More sharing options...
nuhi Posted July 7, 2007 Share Posted July 7, 2007 Did you disable Windows Management Instrumentation in the Services after installation? Check if it's running. Link to comment Share on other sites More sharing options...
MagicAndre1981 Posted July 7, 2007 Author Share Posted July 7, 2007 no. I thinks it's a problem with some integrated hotfixes. I did it the same way like with XP. First I've integrated all my fixes with the tools from the WAIK. Now I started vLite and remove the things you see in the INI-file. I checked the cbs.log and found that the WCP wants to read a file from a hotfix for SideShow, but I removed it with vLite. So the WCP fails to deinstall or install a new Windows Component. I tried to delete the keys from the hotfix in the registry, but this doesn't work I have to check my updates first and must leave fixes out for components that I'm going to remove. Link to comment Share on other sites More sharing options...
nuhi Posted July 7, 2007 Share Posted July 7, 2007 Aha I see. I believe you're right. That's why we had issues when Winsxs folder was cleaned. This is the same issue only selective in nature.Let me know what you find out, I'll see about cleaning the integrated hotfixes from the removed files...but I doubt that. Maybe the solution is in leaving the components in the cache but I would hate that, it could exist only as optional. Link to comment Share on other sites More sharing options...
MagicAndre1981 Posted July 8, 2007 Author Share Posted July 8, 2007 I tried to remove the entires from the registry but I still got an error. The progressbar runs to the end and then a MessageBox pops up. But the confusing thing is, that cbs.log doesn't show an error. Do you know all places where Vista reads to get infos about the packages? Link to comment Share on other sites More sharing options...
nuhi Posted July 8, 2007 Share Posted July 8, 2007 Ok try to integrate after vLite. Other user says it helped. I will be checking if that is possible to change. Link to comment Share on other sites More sharing options...
MagicAndre1981 Posted July 8, 2007 Author Share Posted July 8, 2007 ok, I will create a new DVD this evening and tell you what happened:) Link to comment Share on other sites More sharing options...
boooggy Posted July 8, 2007 Share Posted July 8, 2007 andrei used vlite and then integrated fixes. it all workedgood luck Link to comment Share on other sites More sharing options...
MagicAndre1981 Posted July 8, 2007 Author Share Posted July 8, 2007 (edited) ok, thanks for your answer. I will try it this way. Edited July 8, 2007 by MagicAndre1981 Link to comment Share on other sites More sharing options...
jamieo Posted July 8, 2007 Share Posted July 8, 2007 I'm surprised (but kind of impressed?) that nuhi would even try to support removal with vLite after hotfix integration. I never considered updating before removal but there are so many variables that I prefer to update after anyway. You would want nLite/vLite to support service packs (when they come out) so you can update your installation source once and use that image over and over in vLite. With hotfixes, they come out so often that you would probably update the hotfixes more than the vLite image! ...once nuhi stops adding new features to vLite anyway Therefore, I keep the output from vLite safe* and integrate hotfixes into a copy of that image. When scripted it's no hassle and takes less than 10 minutes. *I actually have the original image stored in the same wim as the hotfixed image. This way it takes up virtually no space as it only adds ~15MB to the size of the wim. Link to comment Share on other sites More sharing options...
nuhi Posted July 8, 2007 Share Posted July 8, 2007 Well that way of doing things, update then configure, is more logical because then the added/updated files and registry entries will be deleted if needed, hotfix won't be firing on an empty place and maybe even leaving the new file which should have been removed.Obviously vLite is breaking those pending integrated hotfix packages since they are working if integrated later (meaning it's not the missing files)...can't wait to find out why. Link to comment Share on other sites More sharing options...
jamieo Posted July 9, 2007 Share Posted July 9, 2007 Well that way of doing things, update then configure, is more logical because then the added/updated files and registry entries will be deleted if needed, hotfix won't be firing on an empty place and maybe even leaving the new file which should have been removed.I can definitely see an advantage for say, adding WMP hotfixes when you only keep the codecs - that way any extra files for the player get removed too. So vLite officially supports this method then? I really didn't expect vLite to account for the differences that future hotfixes may introduce - although now I think about it, that information will be recorded in the installation and I guess vLite reads that info just as it does for a regular installation to find out what components are available... Hmm... I'll have to try this as I'm interested to see what space savings can be gained with this method. Obviously vLite is breaking those pending integrated hotfix packages since they are working if integrated later (meaning it's not the missing files)...can't wait to find out why.I look forward to seeing this fix in the changelog as I'm sure there are others who did not realise this was supported. Jamie Link to comment Share on other sites More sharing options...
jamieo Posted July 9, 2007 Share Posted July 9, 2007 (Had to test this...) I exported two ultimate images from the original source wim and tried applying hotfixes before and after vLite. The hotfixes I applied were all the system updates (no languages etc) offered from Windows Update for the vLited image except for MRT. I also added Hold 'em, XPS Standalone Viewer, HLP viewer and WUSA update. Size increase from applying hotfixes2,163,015,542 Original Vista Ultimate2,218,518,208 Ultimate + hotfixes------------- 55,502,666 = 52.93 MB------------- 565,244,937 vLited Ultimate Image 623,685,049 vLited + hotfixes------------- 58,440,112 = 55.73 MB-------------Notice above, the size increase gained by applying hotfixes to the vLited image is almost 3MB greater than from applying to the original image - which seems to indicate that some of the difference shown below is due to replacing files that have just been removed by vLite.Size difference of each final image 623,685,049 Ultimate -> vLite -> hotfixes 617,390,695 Ultimate -> hotfixes -> vLite------------- 6,294,354 = 6.00 MB (11.34% of original hotfix increase)-------------Not a huge difference but enough to show that vLite is doing some nice cleaning up after applying hotfixes. Link to comment Share on other sites More sharing options...
MagicAndre1981 Posted July 16, 2007 Author Share Posted July 16, 2007 This issue is fixed with vLite 1.0 Final. Thanks nuhi Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now