Jump to content

shhnedo

Members
  • Posts

    64
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by shhnedo

  1. It's kind of a bad idea to use these iso's. Badly made. Better make your own with simplix updatepack and addons from aboddi.
  2. Working solution: Russian / English Same thing, different forum language. Whichever one suites you better.
  3. Same as your VC redist addons - works perfectly fine with the simplix updatepack 19.6.15.
  4. Both the latest updates(2019 and AIO) work perfectly fine with simplix's 19.6.15.
  5. @prihozhanin Жди updatepack 19.6.15. EN: Wait for updatepack 19.6.15.
  6. Because the updatepack works ONLY on the install.wim. boot.wim manipulation was never intended or implemented. No conflicts. And anyway, servicing windows 8.1/10 isn't fully supported under windows 7. Conversely, windows 7/8.1/10 images can be serviced under windows 10. Simply having and using the adk from a newer OS doesn't provide full support for servicing newer OS images relative to the host OS.
  7. Just use simplix updatepack on a turkish iso. https://forums.mydigitallife.net/threads/simplix-pack-to-update-live-win7-system-integrate-hotfixes-into-win7-distribution.45005/
  8. Perfect opportunity to test the April simplix updatepack. Thanks! Edit: Works perfectly right off the bat! No renaming/voodoo magic necessary.
  9. His own words: It's easier to update one small addon for one single version. And I fully agree. Plus, there are the fundamental differences between old runtimes(2005-2008) and new ones(2010+).
  10. @Pavel 2015=2017=2019. 2019 replaces 2017, just like 2017 replaced 2015. You can see the version number is still 14.xx.xx.xxx. When microsoft actually adds a new, standalone version of VC++(for example 2020 or 2021 or whatever), they'll probably change the version number to 20.xx.xxx or 21.xx.xxx or whatever. This number usually corresponds to the last 2 digits of the year when the version is released(at least that's MY understanding). Usually there's no sequence, but for OCD sake - first old SxS addon, then 2013d, then 2019.
  11. The ones that have WinAll or Win810 in the file name.
  12. Both links seem to be working fine. The problem is on your end.
  13. More like "Why is there a "DESIGNER" folder in one of the addons?".
  14. Always run Win Toolkit as administrator. Use folder path with no spaces in it. You might want to describe how you're using Win Toolkit.
  15. Uninstall your 8.1 kit and download the latest one from MS. https://go.microsoft.com/fwlink/?linkid=873065 Then add the path to the new dism.exe in wintoolkit. That should do it.
  16. You're using a pre-SP1 windows 7? Actually, scratch that, it started a chain of ram consuming error reports on my 7 pro x64 sp1. @Legolash2oError_18-05-07_003030.zip This is the first one. Every other error report zip that followed just had more screenshots inside.
  17. I'm not experiencing your issue. http://www.wintoolkit.co.uk/Home/TestBuilds/ 1.6.0.11 seems to be fine.
  18. I'd like to bring this up one more time(v1.6.0.7). Everything else is integrated properly into all selected images. Addons are integrated only into the first image. @Legolash2o Is it possible to fix this?
  19. @OnePiece How do I use the 02.09.2017 update to extract a cab file, or to make a cab file? You mentioned this in your explanation on how to update .netfx addons.
×
×
  • Create New...