Jump to content
Unantastbar

Win Toolkit - Current Version (1.7.0.13)

Recommended Posts

Posted (edited)

On Thursday the 02.01.2020 I have quietly and secretly published v1.7.0.9. The one or other has already noticed it.

But now for those of you who didn't notice.

Win Toolkit v1.7.0.13 was released.

*1.7.0.13: FIX: Enable Legacy .NET Framework [Win 8/10]
*1.7.0.12: FIX: Extended Windows 10 Support
*1.7.0.11: Removed: Donate > Bank Transfer
*1.7.0.11: Moved: Tweaks > Enable Legacy .NET Framework [Win 8/10] to System     
*1.7.0.11: Moved: Tweaks > Custom Explorer Bars (MANIKANT.S.GUPTA) to Explorer
*1.7.0.10: Extended Windows 10 Support
*1.7.0.9: Minor Code changes
*1.7.0.9: Small UI changes    
*1.7.0.9: NEW: All-In-One Integrator > Tweaks > Windows Update [Win 10]
*1.7.0.9: Added "Tweaks" - Disable Automatic App Updates
*1.7.0.9: Added "Tweaks" - Disable Automatic Driver Updates
*1.7.0.9: Added "Tweaks" - Disable Automatic Windows Update
*1.7.0.9: Added "Tweaks" - Disable Automatic Maintenance [Win 10]
*1.7.0.9: Added "Tweaks" - Block in Firewall | Remove Block in Firewall [Win 10]
*1.7.0.9: Added "Tweaks" - Show/Hide Windows Insider Page from Settings [Win 10]
*1.7.0.9: Removed "Repacks.net" > Main Menu Tab (Installer Repacks > Downloads > Integration)    
*1.7.0.9: Removed "Tweaks" > Microsoft Edge

Download

Edited by Unantastbar

Share this post


Link to post
Share on other sites
1 hour ago, stashekmajcherc said:

where is the link to download 1.7.10 mooms.Thanks in advance.Great news!

First post in this thread, on the bottom 😁!

Share this post


Link to post
Share on other sites

@Thiersee & @Unantastbar

In WTK 1.0.11 I'm getting an error when I keep WIM Images mounted to extract winre.wim from System32/recovery and update it with latest updates. The error is something like this "You need to use WTK 2.x and above to use this feature".

I can't keep the WIM Images mounted too for DISM Servicing! After getting the error msg like above. I re-mount the same wim file and then choose Discard to prevent that error. Even the unique filename for Wintoolkit_xx folder in C or any drive uses older reference which conflicts the entire process.

I think file handler is getting cleaned for mounted images if we choose Keep Images mounted!

I'm using Win 10 v1809.

I'm not seeing anything in logs.

Microsoft_Windows_Setup_(x64)_74772.log Microsoft_Windows_Setup_(x64)_83527.log Microsoft_Windows_Setup_(x64)_86816.log

Share this post


Link to post
Share on other sites
4 hours ago, vmk said:

The error is something like this "You need to use WTK 2.x and above to use this feature

*1.7.0.12: FIX: Extended Windows 10 Support

Try again with v1.7.0.12

Share this post


Link to post
Share on other sites

Tried 1.7.0.13 with Windows 7 x64 and latest UL: WTK RunOnce installer did not launch. Tried two times.

1.7.0.8 works.

image.png.ccf4127e0044e05d9fec2d0ef4ce6b42.png

Share this post


Link to post
Share on other sites
26 minutes ago, mooms said:

Tried 1.7.0.13 with Windows 7 x64 and latest UL: WTK RunOnce installer did not launch. Tried two times.

1.7.0.8 works.

I can confirm it!

I wanted to archive all my Win7 stuff and I had to use version 1.7.0.8.

Share this post


Link to post
Share on other sites
On 1/15/2020 at 9:52 PM, Unantastbar said:

*1.7.0.12: FIX: Extended Windows 10 Support

Try again with v1.7.0.12

That's worked. Thanks.

So what was the issue? Was it a bug? Thankfully it didn't break my custom 1809 Image and Image is working fine.

All good!

Share this post


Link to post
Share on other sites

@mooms

Sry, my mistake

in v.1.7.0.13 WinToolkitRunOnce Required .NET Framework 4.8

*1.7.0.14: WinToolkit Required .NET Framework 4.7.2 and higher
*1.7.0.14: Updated WinToolkitRunOnce.exe to v1.6.0.0
*1.7.0.14: WinToolkitRunOnce Required .NET Framework 4.7.2 and higher

 

v.1.7.0.14 comes next Week - this is also the last version for 1.7.0.x

v1.8.x comes Soon . . . (with Language Suppoort)

Edited by Unantastbar

Share this post


Link to post
Share on other sites

@Unantastbar what does that means ?

What 1.7.0.14 will require to WinToolkitRunOnce to run ?

In my setup, dotnet 4.8 is precisely installed by WinToolkitRunOnce, so any dotnet higher than 3.5 will not run before.

Share this post


Link to post
Share on other sites

Hi mooms,

I think the issue is the OS you are using to build an ISO for Win7!

Try now with the realeased version 1.7.0.14, I didn't test it yet.

Have a nice weekend.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Similar Content

    • By Samsunday
      I've spent a whole day trying to make a slipstreamed Windows 7x64 ISO with Wintoolkit. The actual integration of 200 odd updates seems to go fine over 2hrs 20 mins.
       
      But the Wintoolkit ISOmaker always produces a huge ISO : 8.6GB, from 4.3GB files in the working folder. And choosing to rebuild the image or not makes an ISO exactly the same size!
       
      I started with a Windows 7x64 SP1 ISO, and I've followed the instructions here to integrate updates. http://www.wincert.net/forum/topic/12103-16-juin-2015-update-list-gdr-pour-windows-7-sp1-x86x64-fr-en-de-es-it/page-1
      I've been using the latest Wintoolkit 1.5.3.21
       
      Is there something I could be doing wrong? I am at my wit's end.
    • By Rata Maldita
      Hola amigos! Siempre he tratado de ser un alumno que investiga, pero esta vez no pude más! y necesito una manita.. verán:
       
      Utilizo compilar imágenes de Windows desde su versión XP con el Update Pack Latino cuando aprendí gracias al amigo Ricktendo. De ahí brinqué tiempo después a Windows 7 y utilizaba RT7Lite para agregar además algunos tweaks, presiento que entre ellos habría alguno que decía "Correr siempre CMD cómo Administrador" así que en verdad nunca tuve anteriormente el problema que ahora estoy viviendo...
       
      Esta ocasión, quize compilar para Windows 8.1 así que comenzé por lo básico y aprendí vía DSIM a agregar y cambiar el paquete de idioma y alguna que otra monería, pero cómo no era suficiente, investigando en internet me encontré el Win Toolkit, así que lo descargué lo leí y gracias a él pude integrar para X86 y X64 al mismo tiempo. Sin embargo hay algo que no logro todavía, en el archivo Autounattended.XML  ya desconecté el UAC (para que no me salga aquella ventana que pregunta si quiero correr equis aplicación o en este caso un script) y esto me permite que al ejecutarse el archivo SetUpComplete.cmd pueda yo agregar automáticamente nuevas entradas al registro. Sin embargo, al iniciar el sistema cuando nos lleva la primera vez al escritorio, si quiero ejecutar otro batch .cmd ya no me lo permite sin indicárle que cómo administrador (ya no aparece la ventana del UAC que pregunta) pero cómo respuesta cuando quiero meter algo desde cmd al registro me indica "Acceso denegado" y esto me tiene de cabeza pues nunca me había sucedido (se lo achaco a que era un tweak del RT7Lite) pero ahora la cuestión es.. que según yo, he revisado de piés a cabeza el WinTool Kit y no encuentro una opción parecida o a lo mejor no la veo!. También he intentado inyectando al registro por ahí en una llave que se llama WindowsNT>Layers y aparentemente esto hace que siempre que abra una ventana de CMD lo haga como administrador, pero no funciona a la hora de ejecutar desde la línea de comandos (RUN) ni abriendo un batch simplemente haciendo dos click  ("Acceso denegado") y entonces estoy tripeado, ó cómo quien dice, ya no le hallo. No he probado el Win ToolKit 2...
       
      Mi problema es que termina el Script del SetUpComplete.cmd y si le pido reiniciar o no, al entrar al escritorio ya no puedo continuar mi proceso de batch porque no puedo meter nada al registro si no se le indica con click derecho que "cómo administrador" o incluso hay programas que si los instalo de forma desatendida pero no cómo administrador y aunque esta sea la cuenta, nadamás no quieren!
       
      Espero haber sido algo claro en la exposición.. Me llamo Daniel...  Muchisimas gracias!
    • By Plast0000
      this issue is in 1.4.32.5 WIN toolkit (I don't know if it's fixed in the current version as I didn't start working with it yet)
      after installing a version of windows (windows 7) when it enters the desktop it shows a triangular windows with win toolkit logo and it shows an explorer and it tells me to choose the partition where I installed windows
    • By Elazahar
      Hola Ricktendo, primero mil disculpa si el topic que estoy realizando esta mal... pero con el tiempo que vengo usando windows 7 me paso que cada ves que reinstalo windows 7 me baja miles de actualizaciones hasta que se pone el al dia tarda muchisimo. Yo aprendi a actualizar mi windows xp sp3 con tus UPL, podrias Enseñarnos como se usar Win Toolkit para integrar los Upl de actualizacion a windows 7 de x86x64? toda la seccion de windows 7 y win toolkit esta en ingles y no encontre nada didactico que me permita aprender.

      Desde ya muchas gracias.
    • By cactustom
      Hello Gentlemen, saw a tutorial on how to use the Win Toolkit and was hooked and currently checking the site for more of these gems.
       
      Check out the tutorial :
      http://youtu.be/HgyfcojGZmc
×
×
  • Create New...