Brave browser has gained popularity very rapidly and many websites have gone into the territory of recommending it. Sadly although the browser kind of offered better performance, it seems that so much advertised privacy and security was a lie.
Several months ago, Brave was involved in a “scandal”. Unfortunately, this incident did not get much media attention, and it’s hard to search for and discover as of today.
There is an article on the Android police website explaining this issue in detail, you can check it here: https://www.androidpolice.com/2020/06/07/brave-browser-caught-adding-its-own-referral-codes-to-some-cryptcurrency-trading-sites/
But to sum things up and keep them short if you do not want to go through the full article, Brave had been injecting their affiliate codes into popular crypto-currency websites. This means that they had been intercepting your traffic, which they promised was secure by the way, and modifying it.
This means Brave Software has access to all of your information on those crypto-currency sites as well. They can see your payments/purchases, and your activity on the websites (through affiliate statistics).
Now some people might point out that they are not interested in crypto or have been visiting some of the sites but the issue still remains and that is they did all of this, without telling the user. They intentionally didn’t tell the user because they knew it would cause backlash and disruption. They knew one hundred percent what they were doing, and they knew it was unethical.
And the point remains if something like this was already done, who knows what will come up in the future. Personal recommendation is to avoid Brave and go back to other browsers.
get-hotfix KB1111111, KB2222222, KB3333333Note: In the command given above, you need to replace “KB1111111, KB2222222, KB3333333” with the actual update KB numbers.
chkdsk /f /r
“This policy setting allows you to specify a list of Plug and Play hardware IDs and compatible IDs for devices that Windows is prevented from installing. This policy setting takes precedence over any other policy setting that allows Windows to install a device. If you enable this policy setting Windows is prevented from installing a device whose hardware ID or compatible ID appears in the list you create. If you enable this policy setting on a remote desktop server the policy setting affects the redirection of the specified devices from a remote desktop client to the remote desktop server. If you disable or do not configure this policy setting devices can be installed and updated as allowed or prevented by other policy settings.”
Users, when upgrading to Windows 10 from Windows 7 or Windows 8/8.1, or when upgrading to a new version, build, service pack, or major update of Windows 10, can encounter error code 0xC1900101, 0x30018. Windows 10 installation fails and stops or hangs. During the installation process, it will reach a certain maximum limit (normally at 6% or 32%) then reverts back to the previous version of the operating system and displays the following message:
We couldn’t install Windows 10. We’ve set your PC back to the way it was right before you started installing Windows 10.
0xC1900101 – 0x30018 The installation failed in the FIRST_BOOT phase with the error during the SYSPREP operation.
In attempting to fix Error Code 0xC1900101-0x30018, it is vital to know what causes this issue. The most probable causes of this error are:
NOTE: If this fails, if possible, you can try using the .ISO file in upgrading.
If you’re using Windows Update in installing Windows 10, you can implement the following:
NOTE: Don’t forget to hit Enter after every command.
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
NOTE: Don’t forget to hit Enter after every command.
ren
C:WindowsSoftwareDistribution SoftwareDistribution.old
ren
C:WindowsSystem32catroot2 Catroot2.old
NOTE: Don’t forget to hit Enter after every command.
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
One of the selling points of Windows 11 was the ability to run Android apps natively in it without the need for any third-party software. It is not a big surprise that even after its release Microsoft is evolving and expanding Windows 11 and its features.
Microsoft is now rolling out an update for the Windows Subsystem for Android on the Dev Channel of the Windows Insiders program. The new version upgrades the core operating system from Android 11 to Android 12.1 (also known as Android 12L), which means the new system and app features in Android 12 and 12.1 are now available on Windows for the first time. However, not the new features in those updates apply to the modified version that runs on top of Windows. For example, one of the main improvements in 12.1 was a dual-pane notification panel for larger screens, but Android app notifications on Windows just show up in the Windows notification panel.
The upgrade also improves how Android apps integrate into Windows. The Windows taskbar will now show which Android apps are currently using the microphone, location, and other system services — similar to many native Windows applications. Toasts messages (the small popups that some apps use for temporary messages) are now displayed as Windows notifications, and the titlebar on Android apps will use the current activity name for the title.
Full changelog
The new update is limited to Windows Insiders for now, but once Microsoft fixes all the bugs, it should start rolling out to everyone on Windows 11 that has the Android Subsystem enabled.