To be quite honest, I don't like the new skinned interface (January 2016). It looks really ugly compared to the "old" one from December 2015. It just seems out of place with the skin that's not native. Not sure why author decided to go this route...
I know, but I still don't understand the decision for skinned version. It just doesn't look good compared to native Windows 10 interface. Plus we need to have two separate binaries for it now and the native one isn't hosted on official webpage/forum, meaning it's so complicated to maintain a downaload mirror. I wish there was just one version with integrated language and skin/native switching option. So you can have all the language files next to the EXE and then select them through a dropdown menu. Enable/disable skinned version using a checkbox or something. It would just be more convenient for translators and users. Just brainstorming.
...At least he is improving and correcting the tool bugs, what matters most...the rest will come with time.
I have a couple questions please... 1. Someone did some toggle tweaking on my W10 pc and they also installed this update tool. Was a toggle tweak used to have to use this update tool? Did my regular windows update get disabled? 2. What updates should I use since I have a W10 OS that came with my pc... My build: Version 10.0.10240 Build 10240 Here are some attached snapshots of my mini tool Thanks for any help
I'm new to W10 and my answer is genuine... If you've followed all my posts for 7 years, people are provocative towards me not the other way around It has been difficult though, now that you mention, to put out fires but accused of starting fires hence called fire starter cause those who view interactions only view/understand partially not big picture I always appreciate peoples help and efforts Thanks for your interest
He is not around anymore cause he was mistreated/unappreciated/unloved here Thanks for your provocative responses ...lol Any real responses are most welcome and appreciated
Just curious cause windows update hasn't given me one update notification and mini tool has, that's why I asked...
Check in Services, make sure windows update service is running, I really don't know, but both work on mine You may wish to run repair options: In ADMIN Cmd Prompt Type Dism /Online /Cleanup-Image /CheckHealth When you use the /CheckHealth argument, the DISM tool will report whether the image is healthy, repairable, or non-repairable. If the image is non-repairable, you should discard the image and start again. If the image is repairable, you can use the /RestoreHealth argument to repair the image. If image is repairable: With ISO Media in CD/DVD tray: (The same media you installed image with) Type in ADMIN Cmd Prompt Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:M:\sources\install.wim:1 /limitaccess press enter on keyboard, wait for it to finish--M would be drive letter of your CD/DVD tray, remember to change M to your CD/DVD drive letter. After that in ADMIN CMD Prompt run sfc /scannow to is just to make sure all is well.
timesurfer, do by chance have any backup images you could put on, go back awhile, then you could tweak the way you wanted, or maybe this is a old hard drive of Slave77's.
Does "Automatic Updates" set to "Notification Mode" mean Windows will notify me of new updates or do I have to run MiniTool manually every time to check for updates and then manually decide what to install myself? If yes, it would be nice if MiniTool could run as resident app and use a scheduler to check for new updates, lets say one a day and if it finds any updates, shows a popup to the user. This would really be convenient. Unles of course, Notification Mode setting means Windows will notify me, in which case it doesn't matter. I just don't recall warning me since I started using MiniTool. Hm.
Version 10.01.2016 Spanish Translation (es-ar) Traducción Español (español-argentina) www .datafilehost.com/d/74eaeed1