Auslogics Disk Defrag: It Was Okay Until Version 8.0.24

Auslogics DiskDefrag utility was a favorite of mine and I've always included it in the suite of useful apps whenever I configure a laptop, be it for work, or for personal use.

I'd recommend it, even for those who says that SSDs should not be defragmented. I'm not going to discuss that. Even Microsoft do SSD defragmentation. But before you jump the gun, read more on this topic, so you know full well -- you are aware on what is and what is not.

In this short article, I will just say this: I used to swear by Auslogics DiskDefrag utility, insisting even to anybody that it is a required function in the laptop, so the machine is kept in tip-top condition.

Not anymore. Starting from version 8.0.24, the app became a nagger. Always popping up a need to upgrade with a non-killable prompt.

Nobody likes that. Especially bosses who would not believe in the first place that Auslogics DiskDefrag is a necessity.

I rest my case.

I no longer endorse that once useful app. And what's more, they removed the portion that I deemed it useful in the first place: defragmentation of SSD.

So from then on, no more of that nagger. No more of that (once useful, but is now useless) piece of junk for me.

I use these words as I am very disappointed on how a company that produces good software - for free - suddenly turns into a nagging machine. Sorry, but then again, I really mean it.

So goodbye Auslogics DiskDefrag. And I'm not trying any of their free software apps again. I'm sick of being nagged. Thanks but no thanks.

Cannot sign in to Visual Studio 2019

We could not refresh the credentials for the account. The browser-based authentication dialog failed to complete. Reason: The protocol is not known and no pluggable protocols have been entered that match.

I've installed Visual Studio 2019 Community Edition. And I was not able to log in since then. So every time I fire up VS2019, I've been getting the nagging reminder to log in to my account and update the license.

Today I was told that in about 2 weeks, the license will expire -- and I will not be able to use the product anymore.

I've been searching the web for any working solution from the start. But I get nothing.

As I am pressed for the fix, I tried to search again. I found one article in the MSDN forums. Here are the steps proposed:

A.
1. Install IE, and make it the default browser.
2. Add the following sites as trusted sites:

• https://login.microsoftonline.com/
• https://account.microsoft.com/account

Proceed with usual log in process.

B.
1. Close Visual Studio 2019.
2. Run the Visual Studio installer (download it again if needed).
3. At the top right section, there is a Provide Feedback link (person icon).
4. Click and Select either Report a problem or Provide a suggestion.
5. You will be required to sign in. Sign in.
6. Now fire up Visual Studio.
7. You should be signed in already. If not, then sign in. And you should be able to sign in.

I tried both, but A did not work. B worked, and now that I am logged in, I was able to renew my [free] license. Now I don't get the error message:

We could not refresh the credentials for the account. The browser-based authentication dialog failed to complete. Reason: The protocol is not known and no pluggable protocols have been entered that match.

Yahoo!

Till then!

22-Nov-2019, 11:12 pm GMT/UTC+8

The Return of the Come Back

16 July 2019

Just to send out a few notes...

So after more than a year of being away from blogging, -- no, not hibernation -- I am going to type down a few of the things that have helped me with my work, and saved me a lot of time.

There's the Outlook unable to access mail file thingy, then the registry edits to make the PC shut down (and start up>) faster, to the creation of system restore point every restart, which proved helpful to a point, then I thought, I restart every day, but I don't do installation every day, or I do multiple installs in a day, so I created my own version of the utility. It works, though still manual. So I target to create a small program for this if I can.

And many, many other things that due to not persistently putting then down to writing, I have forgotten over time, and so if the issues ever come back again, then I will need to type them all down.

For my own reference and use, of course, and if these would be of any help to anybody else, even just one person, then so much the better.

Short note for now. And I will be on the details in my next posts.

Thank you, and till then!

Huawei Mate 10; Install TWRP, Run Firmware Update, Root With Magisk

Run Firmware Update using this method here:
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279

Root with Magisk using this method here (2nd part):
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956

15-Second ADB Installer
https://freeandroidroot.com/download-15-seconds-adb-installer/

TWRP and guide is from here:
https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904

Similar guide is also here:
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956

Steps (read through at least 1 time to know and be prepared):

Installing TWRP
1. adb reboot bootloader
2. fastboot flash recovery_ramdisk [ Filepath\TWRP.img ].
>  I put the TWRP .img file in C:\adb folder, so I simply type
>  fastboot flash recovery_ramdisk TWRP.img (for my case, that is twrp_bla_alp_0.7.img)
3. fastboot reboot (to restart phone)

N.B. As soon as you execute the restart command, UNPLUG the USB cable and keep pressing Volume UP, so the device will boot to TWRP. This is to avoid the device booting to OS, overwriting TWRP recovery.

Installing Magisk (using adb)
If you did not issue 'fastboot reboot' command in step 3 above, you do this
1. adb reboot recovery
2. adb sideload [ Filepath\Magisk.zip ]
>  for me, that will be 'adb sideload Magisk-v16.0.zip'

But I usually do 'Installing TWRP' procedure up to reboot, and do my Magisk flashing using phone menu, not adb method. You are free to try and choose your own way, too.

When you are done, welcome to a rooted and working Huawei Mate 10 phone!

Thank you and till then!


Drafted on 20-Jun-2018