Updated Default Permissions for Windows 10 to the newest Windows Updates. This should now keep any users from getting stuck in safe mode (They do NOT stay installed as a service on the system, they run once and then are removed) The new files (TweakingRemoveSafeBoot_32.exe and TweakingRemoveSafeBoot_64.exe) will install as a service and when they run (Services can run at the login screen) they will run the “bcdedit /deletevalue safeboot” command and then remove itself as a service. So I have built a new service that is installed when you tell the main program to boot into safe mode.
but if the user couldn’t get logged in then they where stuck. One way out of safe mode was to use msconfig.exe to remove it. But if a user couldn’t get logged in for some reason, or they didn’t run the main program in safe mode they would always boot into safe mode. Once the main program is ran in safe mode it would run the command to remove safe boot. Currently the main program calls the bcdedit command to set the safe mode with networking boot option. Built and added a new tool for booting out of Windows Safe mode. Updated safe mode code in the program to allow a few more services to run in safe mode with networking. Updated 7-zip extract file “7za.dll” to v15.12 Updated Windows 10 Default permissions to all updates installed as of 12-14-2015. Updated default permissions for Windows 7,8 & 10 with all updates as of Feb 16, 2016. By having the option checked by default the program will always try to add the cat files back, as long as their signatures are good, back to the database, preventing any false bad signatures. The reason for this is that if a user had deleted and rebuilt their catroot folder and database then a lot of the cat files would be missing, returning a LOT of bad signatures in the pre-scan.
CAT Files (Security Catalog) To Windows Catalog Database” in the pre scan tool is now check marked by default. Updated and improved the built in pre-scan tool. Large amount of code changes and updates. Updated default permissions for Windows 7,8 & 10 with all updates as of May 16, 2016. In this case needing to know what current build Windows 10 is, this can be helpful. While this doesn’t change any repairs it is more for information on what version of Windows the program is currently on so the user can see it. Updated the repair list to have the current version of windows in top of the list. The minimum build number Windows 10 must have for the repair to work is 10586.318 or higher, anything lower and the program will skip the repair. Now that this has been fixed I have enabled the repair for Windows 10 again. The Repair Windows 8/10 App Store has been re-enabled for Windows 10! In the May 2016 update to Windows 10 Microsoft finally fixed the 7 month old bug where calling the powershell commands to install the apps would break a large portion of them.
0 kommentar(er)
