My tools are based on the white paper for push-button recoverry from Microsoft. all the recent computer I had in the past years was build around the same thing 1) Windows on 1 partition 2) Booloader on another one 3) Recovery tools on another one My tolls put the recovery package (apps + drivers) on the same partition as Windows. My dell computer (XPS 8930) had them on another partition and was using junction point on the Windows drive to point there. But, yes, most OEM manufactuyre use solution around the same receipt.
Hi everyone! Version 6.1.0 is out! - Support for Windows 11 25H2 - Slimmer "Required Packages" file since 25H2 file are backward compatible to previous version so I removed them - New software icons - Options (Default) to remove all APPX package from the user running SYSPREP. Found out that sometime drivers, app (like Notepad++) add packages which break Sysprep. Since the user will be destroy, no point to keep them! - Add the recovery icon + command prompt to the taskbar [Windows 10 + 11] - Add the recovery icon + command prompt to the Start Menu [Windows 11] [This can be modified by editing two files - XML and JSON - in the settings folder - Info in the doc - You can use that also to launch custom software, link to web page, etc.] - New version of DoubleCommander for the WinRE part - Newer version af AutoIT interpreter for the script - Newer version of ClamWimPortable in the recovery menu PS : Next version will probably have a new color/icons scheme to fit the default one of Windows 11 (blue tint or similar)
This is probably the absolute easiest thing to do and we all love a cleaner install. I still whonder if it can be fixed within the batch with a for loop that finds installed userpackages and uses "Powershell.exe Reset-AppxPackage -Package "<nameofappx>" "
Version 6.1.1 is out! New : Option to opt-out of the Start Menu and Taskbar customization Fixed: If Start Menu and Taskbar customization is enabled, it persist after a push-button recovery Changed : New colors and icons for the software Thanks for you habitual support for my project! EDIT : Version 6.1.2 is out Fixed : I forgot to change th eicons of the recovery media (full-wim) to match the new color. Now fixed. 6.1.2 is just a esthetic fix.
Out of subject ... if you look at my signature, I made a small project for myself to use a Raspberry Pi Zero 2 as a multi-usb drive. Similar to IODD deivce but with different functionalities (less image support, more network option). Do you know if I can post a page for that new project here or shoudl I seek to find a forum specialised on Raspberry Pi project?
A Raspi is usually a small, portable SOC system. I guess the Mobile and Portable forum should be the best location? General OS software questions can also be clarified in the Linux forum, as Raspis and Arduinos usually run a Linux variant.
I did a quick update. 6.1.2. Just a visual fix. When using the "full-wim" option, the menu in the recovery media was using the old icons but with the new background color. Just fixed that.
Bonjour Anarethos, Encore une excellente mise à jour du projet. Lorsqu'on utilise l'option « full-wim » dans le menu du support de récupération, est-il possible d'ajouter une image de fond ? J'ai essayé de le placer dans « Windows 1X Recovery Tools\Recovery\OEM\WinREFiles\recovery\Windows\System32\winpe.jpg et winre.jpg ». mais ça n'a pas marché. Hello Anarethos, Another excellent update to the project. When using the “full-wim” option in the recovery media menu, can we add a background image? I tried putting it in “Windows 1X Recovery Tools\Recovery\OEM\WinREFiles\recovery\Windows\System32\winpe.jpg and winre.jpg,” but it didn't work.
Hi everyone! I made an "add-on" for my tools. Download link in the first post. Here are the details When I created the first versions of my tools, I was using TrueCrypt and Windows XP. When TrueCrypt was discontinued by its author, I switched to BitLocker and adapted my tools to work with it. In fact, I didn’t really have to, since BitLocker support was already built into the product. Although I was using TrueCrypt’s successor, VeraCrypt, I was not using it for full disk encryption and never thought about bringing back support for a TrueCrypt successor in my software. But then YellowKey happened, and I lost trust in BitLocker. I also realized that I am probably not alone! So I decided to go back to the drawing board and see if I could add VeraCrypt support to my tools. By default, my tools were already “somewhat” compatible with VeraCrypt. You *just* had to completely decrypt your Windows installation before using the Windows Recovery Environment to repair and/or reinstall Windows. I wanted to give users the ability to access offline files, repair basic boot problems, and roll back Windows updates—all without decrypting the drive. Bonus if it could also allow Windows reinstallation. Hence this package, which acts as a “VeraCrypt enabler” for my recovery tools. With it, once the boot password is provided, the Windows Recovery Environment can access the Windows installation transparently and perform repairs. It can even perform a push-button reset while preserving encryption, whereas BitLocker-encrypted drives must be re-encrypted afterward. That said, this is still a work in progress, and bugs may occur. Keep backups and do not lose your VeraCrypt recovery disk! -- DIRECT DOWNLOAD LINK REMOVED -- Now included in 6.1.3 and up!
Juste to let you know that I am working on version 6.1.3 that : - Will support Windows 11 26H2 - Add Spanish support (thanks to ChatGPT for the translation lol) - Updated version of ClamWin + DoubleCommander - Built-in Veracrypt support (AddOn folder) - No need to download an external package Currently in the testing stage. Hope to have it later this week or next one!
Version 6.1.3 is ready! Added: Support for Windows 11 26H2 Added: Support for VeraCrypt Added: Spanish translation (made with ChatGPT from French version) Updated: DoubleCommander, ClamWinAV, Update script, WinRE Password tool Changed: Language selector in place of automatic language detection The reason for point 5 is that there is multiple region code for spanish, french, english, etc. And if a user was using one not targetted in my settings file, it automatically went to english. Now the user has the choice.