Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

alvinkhorfire

Member
  • Posts

    104
  • Joined

  • Last visited

  • Donations

    $0.00 

Posts posted by alvinkhorfire

  1. x64

    dism /online /Remove-ProvisionedAppxPackage /PackageName:Microsoft.Bing_1.2.0.137_x64__8wekyb3d8bbwedism /online /Remove-ProvisionedAppxPackage /PackageName:Microsoft.BingFinance_1.2.0.135_x64__8wekyb3d8bbwedism /online /Remove-ProvisionedAppxPackage /PackageName:Microsoft.BingMaps_1.2.0.136_x64__8wekyb3d8bbwedism /online /Remove-ProvisionedAppxPackage /PackageName:Microsoft.BingNews_1.2.0.135_x64__8wekyb3d8bbwedism /online /Remove-ProvisionedAppxPackage /PackageName:Microsoft.BingSports_1.2.0.135_x64__8wekyb3d8bbwedism /online /Remove-ProvisionedAppxPackage /PackageName:Microsoft.BingTravel_1.2.0.145_x64__8wekyb3d8bbwedism /online /Remove-ProvisionedAppxPackage /PackageName:Microsoft.BingWeather_1.2.0.135_x64__8wekyb3d8bbwedism /online /Remove-ProvisionedAppxPackage /PackageName:Microsoft.Camera_6.2.8514.0_x64__8wekyb3d8bbwedism /online /Remove-ProvisionedAppxPackage /PackageName:microsoft.microsoftskydrive_16.4.4204.712_x64__8wekyb3d8bbwedism /online /Remove-ProvisionedAppxPackage /PackageName:Microsoft.Reader_6.2.8516.0_x64__8wekyb3d8bbwedism /online /Remove-ProvisionedAppxPackage /PackageName:microsoft.windowscommunicationsapps_16.4.4206.722_x64__8wekyb3d8bbwedism /online /Remove-ProvisionedAppxPackage /PackageName:microsoft.windowsphotos_16.4.4204.712_x64__8wekyb3d8bbwedism /online /Remove-ProvisionedAppxPackage /PackageName:Microsoft.XboxLIVEGames_1.0.927.0_x64__8wekyb3d8bbwedism /online /Remove-ProvisionedAppxPackage /PackageName:Microsoft.ZuneMusic_1.0.927.0_x64__8wekyb3d8bbwedism /online /Remove-ProvisionedAppxPackage /PackageName:Microsoft.ZuneVideo_1.0.927.0_x64__8wekyb3d8bbwe

    Could you update the script for Windows 8.1? Thank you for your help.

  2. @nice_guy75

    Thanks for your summary. Is your method of using vLite primarily based on dead0's guide?

    @bphlpt

    I agree with what you said regarding Windows 7 Toolkit. The problem is that it does not remove components as many as RT 7 Lite. And, I don't think that I can make this request, which is not in line with Legolash2o's original intention.

    Source

    Kelsenellenelvian said:

    He really isn't going to add more as the way he removes things are the dism way, NOT the hack way.

    i.e. DISM only allows for removal of packages and is kinda limited.

    Plus he is not trying to compete with vLite or rt7lite...

    I am sure that some of us would like to have smallest Windows image as possible, without overly affecting its stability.

  3. Sorry, can anyone provide an honest and unbiased assessment in comparing between Windows 7 Toolkit, RT 7 Lite and vLite? I realize that each software has its own pros and cons. Can Windows 7 Toolkit perform what RT 7 Lite can do, and achieve a very slimmed-down stable image?

    In term of component removal, which software can remove more components?

    No ill intention is intended. I just want to know what the best tool is. :)

    Thank you for the information.

  4. @myselfidem

    Off topic a bit, you could choose to post a direct link to the post. On the upper right corner of each post, is the post number, such as #153 in this post. Right click the post number and copy the direct link of the post. That way, your post would contain the direct link to the indicated post, instead of having other readers manually scrolling down the page to find the quoted post.

    Anyway, I notice that you always try to answer many inquires in this forum and try to be as helpful as you can. It is a definitely commendable effort from you. Keep up the good work. :thumbup

  5. @vincentvega007

    Sorry for confusion. I was not questioning your ability of slimming down Windows. Anyone using a customized Windows 7 SP1 with IE 9 integrated, should not be installing IE9, because it has been integrated. That is why I found it weird that you have to install IE 9, as if you did not integrate IE 9 at all.

  6. Breaking news on RT 7 Lite 3.0 as provided by the administrator of RT Seven Lite Forum:

    I quote the entire message here for your convenience:

    Dear visitors and members,

    We are working on a brand new version with easy pick up mode to avoid complexity. New version will arrive soon by next month July 2011. New version will be available for Home users as well as for commercial use to deploy. We no longer provide support for all previous versions. Thank you for your co-operation.

    Regards,

    Rockers Team

  7. About spoiler! ;)

    At last

    Well, I did realize my "/spoiler" mistake yesterday, but somehow post editing did not allow me to edit the post throughout yesterday. :wacko: Luckily, I managed to correct it just now.

    Thanks for head-up, myselfidem. :)

  8. @myselfidem

    Thanks for sharing your method of customzing Windows. It is good to know other prespective and opinion in modifying Windows.

    Have you tried protecting werconcpl.dll, I am thinking of doing so.

    Just protect werconcpl.dll and you should be able to remove Error Reporting with no problem. Here is my list of protected files, which I gathered from various guides here. It is a bit overprotective, but it is better to be safe than sorry.

    windows\system32\browcli.dll

    windows\sysWow64\browcli.dll

    windows\system32\Magnification.dll

    windows\sysWow64\Magnification.dll

    windows\system32\msdrm.dll

    windows\syswow64\msdrm.dll

    windows\system32\msdt.exe

    windows\system32\msoert2.dll

    windows\syswow64\msoert2.dll

    windows\system32\optionalfeatures.exe

    windows\syswow64\optionalfeatures.exe

    windows\system32\SystemPropertiesRemote.exe

    windows\system32\tbs.dll

    windows\system32\wer.dll

    windows\system32\werconcpl.dll

    windows\system32\wercplsupport.dll

    windows\system32\werdiagcontroller.dll

    windows\system32\wiaaut.dll

    windows\SysWow64\wiaaut.dll

    windows\system32\winipsec.dll

    windows\system32\wmdrmsdk.dll

    windows\SysWow64\wmdrmsdk.dll

    windows\system32\wlanapi.dll

  9. @myselfidem

    So, for your customized Windows 7 SP1, you do not remove any components. I guess that component removal may cause quite a bit of problems for all of us. Thus, what do you modify in your customized Windows 7 SP1, rather than integrating updates and drivers? Do you use other software rather than vLite in constructing your image? Pardon my curiosity here, but it would be good for me to learn how other experts like you in modifying the Windows image.

  10. @ vincentvega007

    I would suggest that you integrate the msu version of IE9 into your image. The direct link for IE9 are as follow:

    Win7

    x86: http://go.microsoft.com/fwlink/?LinkId=210145

    x64: http://go.microsoft.com/fwlink/?LinkId=210143

    I mean, you really do not have to wait after Windows installation, to use Windows Update to install IE9.

    As for some updates failed to be installed, I believe that the updates tried to update some components you have removed via vLite, and thus failed. I do encounter such case for my slimmed-down Windows 7 SP1. There is nothing much you can do, rather than rebuild a new image by integrating all newer updates before using vLite.

  11. @bapt

    Thank you so much for your explanation. You are very helpful. :thumbup

    For me, after using RT 7 Lite as suggested in your steps, I would suggest executing the batch removal file via Gimage to remove redundant fonts. This batch file originates from dead0's guide. That way, we can achieve further slim down of the image.

    So, you remove winsxs via RT 7 Lite. Can you install Windows updates to your Windows?

    Everything looks good except windows update - updates some reports that have not been successfully installed - for example internet explorer 9.

    Do you integrate the msu version of Internet Explorer 9 into your image before using vLite? Do you remove winsxs?

  12. but the software. came out before the sp1 pre integrated isos came out.

    You can use RT 7 Lite 1.7.0 RC to slim down Windows 7 SP1 (MSDN) image and it will work well. This is how I create my customized Windows. RT 7 Lite 1.7.0 RC will treat Windows 7 SP1 as if it is just Windows 7 RTM with no Service Pack, so the integration and component removal will remain just the same.

    You do not have to use RT 7 Lite 2.6.0 Beta, since SP1 has been integrated inside the MSDN image.

  13. bapt

    Thank you very much for replying to my question and supplying your preset. :thumbup

    1. So, how do you integrate Windows update? Is it via DISM?

    2. As for integrating drivers, do you use RT 7 Lite to integrate drivers?

    3. I understand your highly recommended solution stating that first use Gimagex, integrate the updates, then vLite and finally RT 7 Lite. For all of this steps, we do not need to install WAIK for Windows Vista and WAIK for Windows 7, right? I only have to insert vista vimfltr and wimgapi.dll in vLite folder.

    Thanks again for your help.

  14. Ok, i have tested this and it works with vLite.

    But since i want to use both vLite and RT 7 Lite, then what should i use first?

    Should i first use RT 7 Lite, then GImageX with you're steps and then vLite?

    Let me know how i have to go forward.

    Me, I use first Gimagex then Vlite and I finally rt7lite

    if we use first rt7lite is an error message launching Vlite about the boot (boot-optimized by rt7lite and not "compatible" with vLite)

    bapt

    I do not really understand what you meant with the bolded part.

    As recommended, I used Gimagex to create a modified wim of Windows 7 SP1 (MSDN). Subsequently, I used RT 7 Lite to integrate Windows updates and remove components. However, after this step, if I use vLite to slim down this image, vLite will stop responding. Is this what you meant by error message launching vLite?

    You suggested to use vLite after using GImagex, but vLite cannot be used to integrate Windows updates to the image. Moreover, we should not remove components prior to integrating updates to the image. By your method "I use first Gimagex then Vlite and I finally rt7lite", could you explain when the time to integrate updates is?

    It would be very helpful if you can share your RT 7 Lite and vLite preset, so that I would know components that should be removed by respective software.

    Thank you very much. :)

  15. In this thread, MagicAndre1981 suggested a way to remove IE 8, for those who have IE 9 installed. I have neither tested it yet, nor thought of a way to integrate the command to RT 7 Lite.

    run this command twice from an command prompt (cmd.exe) with adminrights:

    FORFILES /P %WINDIR%\servicing\Packages /M Microsoft-Windows-InternetExplorer-*8.*.mum /c "cmd /c echo Uninstalling package @fname && start /w pkgmgr /up:@fname /norestart"

    this should remove the IE8 files with the help of the command line.

    Make a backup first.

  16. I did not integrate anything. I use your ini and inf (sp1_v2) but I keep some stuff you selected. For example Japanese language in vLite is selected (needed for Office 2010) and Windows Mail is selected (needed for Office 2010) and a couple of drivers and other stuff.

    Sorry, could you provide more explanation on keeping Japanese language and Windows Mail (needed for Office 2010)? I believe that you only need to keep Japanese language, if you use RT 7 Lite to slim down Windows 7. You can use vLite to remove Japanese language, and yet you should have no problem to install Microsoft Office 2010 in the resultant slimmed-down Windows 7.

    As for now, I do not really why the removal of Windows Mail would affect the successful installation of Office 2010. :unsure:

    Thanks for the explanation given.

  17. The 1.7 version has a new way to integrate the drivers; RT7 Lite puts the Nvidia drivers in a folder called CustDrivers in the Windows directory, They are installed only after you reboot the computer after installation. I prefer the old fashion way, but I guess it didn't work so well and he had to come up with an alternative method.

    I would prefer the old fashion way as well. Once the Windows installation is completed and it boots into desktop, the video card driver is fully installed and no further tinkering is required.

    The current method used by RT 7 Lite to integrate drivers do not work quite well for me. This problem happens in both of my computers, one with nvidia video card; the other with AMD video card. Once the Windows installation is completed and it boots into desktop, the video card driver is not yet installed. If I restart the computers, the integrated video card driver seems to "disappear" from it, as if no video card driver has been integrated.

    To solve this problem, once the Windows installation is completed and it boots into desktop, I have to immediately open the Device Manager to access the video card. A prompt to restart Windows pops out. Only then, I shall restart the computer. Upon restart, only then the video card driver is fully installed.

    It is quite frustrating for me. After all, the reason of using RT 7 Lite to slim down Windows, is to have everything (drivers, Windows Update and etc.) fully installed upon first bootup into desktop. For now, I have to perform extra steps of accessing Device Manager and restart the computer. These extra steps provide unnecessary inconvenience for me. :(

    Guys, is there any way to solve my problem? Thanks for the advice given. :)

  18. InstallWimTweak.exe can do this but it does all packages, not just IE8

    If anybody knew exactly what InstallWimTweak.exe does it could possibly be done manually just for IE8 package

    Do you mean installwimtweak by wnuku, used in vLite threads, such as Windows 7 Ultimate/Server 2008 R2 Enterprise SP1 Batch Removal?

    Here is wnuku's reply in regards to the function of the installwimtweak.

    hi,

    yes, i created install wim tweak some time ago, and purpose of it was to enable removing some components of windows. And simply, only thing that install wim tweak is doing is changing registry entries inside hives in install.wim (sorry for misleading name of tool). Back in 2008, guides about removing components from vista/2008 had instructions how to do all those changes manually, but it was time consuming and could cause many errors when registry has been edited in wrong way. That's why i created this tool - to simplify this process. If you are curious what exactly my tool is doing, there are source codes posted here : http://www.msfn.org/board/index.php?app=forums&module=forums&section=findpost&pid=825130 .

    Short answer, as far i can remember, install win tweak does not touch file security inside install wim. Hope it helps :)

    Hope this helps, ricktendo64. :)

  19. MagicAndre1981

    Thank you once again for recommending this nifty tip. My questions are:

    1. With IE 8 removed, will IE 9 continue to run fine without any problem? In other words, is IE 9 made to be independent of IE 8, without using any IE 8 files?

    2. I am currently a slimmed-down Windows 7 SP1 with IE 9 slipstreamed by RT 7 Lite. Is its safe to use this command, without harming my system?

    Thanks for the advice given. :)

  20. if SxS could be removed without fatal bugs, that would be the only thing "needed" for win7 to be light

    rest is just page file size :P

    Referring to dead0's thread, you can use the batch file to safely shrink winsxs, without affecting the ability to use Windows Update.

  21. I've used the RT 7 lite but it's so much buggy and don't want to try it again.

    Sorry, could you clarify why and how RT 7 Lite is buggy? Are you employing a preset that removes way too many Windows components, causing dependency problems? Or, are you using some form of hardware (camera, printer and etc.) that may need certain Windows components which cannot be removed? If you can shed more details here, other experts will be in better position to assist you.

    My advice would be to use RT 7 Lite 1.7.0 RC to slim down Windows 7 SP1 (MSDN) image, rather than to use RT 7 Lite 2.6.0 Beta to slipstream SP1 to Windows 7 RTM image and then slim down it. It is much more stable that way. The slimmed-down Windows 7 SP1 by RT 7 Lite 1.7.0 RC is what I use in my computer and it is stable to be used.

    And i would like to request you vlite guys to make a windows 7 version.

    Asking others to create a Windows 7 SP1 Lite for you is not a good idea, since every one has its own way of using Windows. The best bet is to use a stable preset from RT 7 Lite forum and customize it to your own need. Start with a preset that removes few components. Once the image based on that preset works well in your computer, try remove more components. Keep working on it and you will have a nice stable Windows 7 SP1 Lite. :) Good luck!

  22. [Did you try to make your DVD unattended, as with v2.6.0 skip user creation is not working and I have enabled the control panel in and HomeGroup was enabled. Though I am more concerned about unattended DVD. If v1.7.0 RC can make unattended DVD it is fine with me.

    If I am not mistaken, the only difference between 1.7.0 RC and 2.6.0 Beta is that 2.6.0 Beta can slipstream SP1 into Windows 7 RTM. Having said that, RT 7 Lite 1.7.0 RC can certainly create unattended DVD, similar to 2.6.0 Beta.

    In Unattended tab of RT 7 Lite 1.7.0 RC, select the following:

    a.General

    Skip product key=True; Skip Auto Activation=True; Accept EULA=True; Select this version on install=True; Fullname="Your name"-PC; Computername=="Your name"

    Click "Add more users". The first account is an administrator, which is you.

    b. OOBE

    Network location=Home; Protect your computer=Recommended Settings; Hide EULA page=True

    c. Regional

    Specify=True

    I strongly believe whatever unattended setting you choose in 2.6.0 Beta should be available in 1.7.0 RC, thus 1.7.0 RC should be able to create Autounattend.xml for you.

  23. I think it's better to use RT Se7en Lte 1.7.0 RC with DVD Windows 7 SP1, because it is more stable than RT Se7en Lite 2.6.0 beta!

    nice_guy75, just heed myselfidem's advice. It works for me. I am running Windows 7 SP1 (IE 9 integrated) slimmed down by RT Se7en Lte 1.7.0 RC in my computer, and it works fine with no problem.

    The only reason to use RT Se7en Lite 2.6.0 beta instead is that you want to slipstream SP1 to Windows 7 RTM image. When using RT Se7en Lte 1.7.0 RC, it does not make any difference if you use Windows 7 RTM or Windows 7 SP1. RT Se7en Lte 1.7.0 will treat Windows 7 RTM and Windows 7 SP1 just the same. :)

    Plus, RT Se7en Lte 1.7.0 RC should be more stable than RT Se7en Lite 2.6.0. With Windows 7 SP1 image, you do not have to waste your time slipstreaming SP1.

    In short, use RT Se7en Lte 1.7.0 RC to slim down DVD Windows 7 SP1, just as myselfidem advised. :)


×
×
  • Create New...