Jump to content

ricktendo

Members
  • Joined

  • Last visited

Everything posted by ricktendo

  1. What what size do the msi uninstall entries say on the NON slim?
  2. You cannot go by what size the original setup wrapper says, its bogus. Do you seriously believe what it says? If you install the using the original setup, go un-hide the MSI uninstall entries in regedit by deleting SYSTEMCOMPONENT key to show in add/rem programs reg del HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID-FOR-DOTNET46-HERE} /v SYSTEMCOMPONENT /f
  3. (Only) INTL version updated to correct LPs not installing Added individual Language Pack and SFX links For those of you having problems downloading from Adf.ly, google "adf.ly link decrypt"
  4. Only the setup wrapper is v30501, the msi version and file versions contained are v21005, you can view this by opening regedit and checking this key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DevDiv\VC\Servicing\12.0
  5. You only need the x64 installer
  6. Can I have a link to the 2013 runtimes?
  7. Updated first post with 4.6 final, intl version will take more time Edit: Intl added, will add sfx and individual lang packs later
  8. Final comming out any minute
  9. No not a mistake, office runtime is separate to the regular runtimes and is only shown if you install office 2k10 I will see about creating a slim aio for them (consist of x86, x64 and 18x2 language packs for them)
  10. Reboot and keep trying /cleanup-wim and /unmount-wim
  11. 7-13-2015 Add: 3057756, 3064706 Rem: 3048074
  12. Then its normal, if you dont uninstall previous version you will need to restart to overwrite older 'in use' files
  13. You can use /y to make silent and /ai /gm2 to make silent and NOT see any install progress
  14. Did you uninstall the previuos hotfix rollup compstuff?
  15. ricktendo replied to Hans Jakobsson's post in a topic in Windows 7
    WinToolkit (and many other gui tools) has the option when integrating drivers to integrate boot critical drivers as well, or you can integrate your driver into boot.wim index #2 and this will solve your problem
  16. Updated 4.0: add KB3057756, KB3064706 (rem KB3048074) Sifnificant superseded reg cleanup for 2.0, 3.0 and 3.5
  17. Updated v10 and v11
  18. Install after login, not during wintoolkit software install
  19. Extraes y abres el instalador.msi en un programa com InstEd u Orca y cambias el Property -> ProductName
  20. Slim, not much time