Upcoming Windows features for future

So, what is Electron bot, and why it even matters if it is in the MS store. Electron bot is malware that somehow found its way inside MS Store via game clones of popular games temple run and subway surfer. This infiltration led to the infection of around 5000 systems over the globe in a very short period of time.

This malware is a backdoor that gives complete system control to the attacker. Any type of execution can be performed remotely in real-time. Usually, this kind of attack was aimed at a spread of click fraud over popular social media like Facebook, google, youtube, etc.

Primary goal

Electron Bot's primary goals in the ongoing campaign analyzed by researchers are:

• SEO poisoning – Create malware-dropping sites that rank high on Google Search results.
• Ad clicking – Connect to remote sites in the background and click on non-viewable advertisements.
• Social media account promotion – Direct traffic to specific content on social media platforms.
• Online product promotion – Increase store rating by clicking on its advertisements.

These functions are offered as services to those who want to increase their online profits illegitimately, so the gains for the malware operators are indirect.

Publishers that contain malware

For now, users may take note of the publishers who released confirmed malicious game apps using the following names:

• Lupy games
• Crazy 4 games
• Jeuxjeuxkeux games
• Akshi games
• Goo Games
• Bizzon Case

As you know, installing Windows 10 is quite a complicated process in the background even though it may look like an easy task in the foreground. There are times when the setup is stuck on the “Hi there” screen where you won’t be able to input any information in the fields given and you wouldn’t be able to do anything else since the screen does not move ahead. There are a lot of possible reasons why this issue occurs. It could be due to a damaged setup image, invalid boot configuration, and many more. To resolve this problem, there are several options you can check out. You can try to get a new setup image or run the Automatic Repair or you could also try to recreate the Boot Configuration files or BCD. To get started in checking out these solutions, make sure to follow the instructions provided below.

Option 1 – Try to run the Automatic Repair Utility

You might also want to use Automatic Repair in fixing the error. To do so, follow the steps below.

• You can start by creating and booting from a bootable Windows 10 USB Stick.
• After that, click on Repair your computer located on the bottom left corner when you are on the initial Windows Startup screen.
• Next, click on Troubleshoot, and then on the other screen, click the Startup Repair option.
• Now select the operating system you want to repair. Once you do that, it will start to repair your operating system. Wait until the process is completed and then check if the problem’s now fixed.

Option 2 – Try to rebuild the BCD files

You can also try rebuilding the BCD files to resolve stuck screen issue in your Windows 10 computer.

• You can start by booting into the installation environment for Windows 10 from an installation media.
• After that, click on Repair your computer and on the blue screen, select Troubleshoot and then select the Advanced options menu.
• From there, select Command Prompt and once you open it, enter each one of the commands given below by sequence.
  • bootrec /FixMbr
  • bootrec /FixBoot
  • bootrec /ScanOS
  • bootrec /RebuildBcd
• Once you’re done executing the commands given above, type “exit” to close the Command Prompt window and then restart your computer and see if it fixed error code 0xc000014c.

Option 3 – Try recreating the Windows 10 installation USB

Recreating the Windows 10 installation USB might help in fixing the problem. You can use a USB drive to do so but make sure that it has a great read-write speed. Follow the steps below to recreate Windows 10 installation USB”

• Click this link and then click the Download Tool Now button.
• Next, click the “Use the tool to create installation media (USB flash drive, DVD, or ISO file)…” option and follow the next given instructions on the screen.
• Now select the ISO file option in step 5.
• After that, you should now have an ISO file.
• Next, go to the location where you’ve downloaded the ISO file.
• Then right-click on the Windows 10 ISO file and select the Open with option and then select File Explorer.
• Now click on “setup.exe” and follow the next instructions that appear on the screen. When asked, you have to select either Nothing (clean install) or Keep personal files only option. Take note that you must not select the “Keep personal files, apps, and Windows settings since it doesn’t really work.

Option 4 – Try getting a new Windows image file

If none of the four given options above worked, you might want to get a newer installation image using the Windows Media Creation tool. After that, create the bootable USB drive and once completed and then try to run the Windows 10 setup again.

On September 18th, 2017, Cisco’s Talos announced that CCleaner, a popular utility with billions of worldwide users, had been compromised by hackers, and was used to unwittingly distribute hidden malware in its installer. Later in the day, Piriform, the publisher of CCleaner, confirmed the problem.

Undetected by all but 1 major antivirus including CCleaner’s own parent company, this occurred for over a month and impacted over 2.7 million users. Users of CCleaner v5.33.6162 and CCleaner Cloud v1.07.3191 for 32-bit Windows are affected. These downloads were live on CCleaner’s official site from August 15th to September 12th, 2017. Anyone who downloaded the program during this time could be affected. The company claims that while the hackers set up the backdoor and many users were impacted, that the perpetrators have been arrested and that the malware never successfully performed its full task and compromised user’s PCs or sent out their data; in the wake of recent security breaches such as Equifax, users are understandably worried. Given the severity of the threat of hacking and data theft, users should take action immediately if they have CCleaner.

Technical Details of CCleaner Malware Injection

First reported by Talos, the malware, which was hidden in the CCleaner installer without the publisher noticing (despite them being owned by Avast, a massive Anti-virus company), modified a core program DLL file to evade detection, and creates several registry keys. Not only were these files not flagged by any major Anti-Virus, but they were also even digitally signed by Piriform via their Symantec certificate, meaning your PC and security program would likely whitelist and trust the malicious installer. The malware gathers personal information on a user’s PC, including IP address and running programs, and sends it to a remote server. In our testing, the program sent data to IP 216.126.225.148.

Restore Your PC (If Possible)

As of the publication of this article, there have been no assurances given that updating or even uninstalling CCleaner will remove the malware is installed. The only action thus far has been shutting down the remote server where user data was being sent has been shut down by authorities. For this reason, it is best to remove the underlying malware separately, as its presence represents a serious security threat. Unfortunately, as this could have been installed as far back as August 15th, 2017, your System Restore points may not go back that far, or even if they do, restoring to such an outdated point may cause unintended problems with other programs you use and potentially lost files and data. Manually backing up files and doing a full format or clean Windows installation would likely be successful in fully removing the malware, but is extremely time-consuming and can be difficult for many PC users. Unfortunately, this makes a PC Restore or format an unattainable option for many.

Update CCleaner to the Latest Version

While CCleaner has told users to update to the latest version of the program. Prior to doing so, we recommend fully uninstall CCleaner, ensuring you check its program files folders and registry keys, manually deleting any remnants, and then re-downloading the latest version from the official site and reinstalling clean.

What Is Runtime Error R6034?

Runtime Error r6034 is one of the most commonly occurring errors.  This error usually arises in Windows Vista and Windows 7. The message that appears to the user states ‘An application has made an attempt to load C runtime library incorrectly, please contact the support team for more information’. As the message suggests, this problematic error occurs simply because an application attempts to load the C runtime library without a manifest.

Solution

Error Causes

Runtime Error r6034 occurs when the system compiler fails to compile the working application. While this is the primary reason, there are some other conditions that trigger Runtime Error r6034 which are outlined below.

• Existence of viruses and malware in the system.
• Corrupt or missing system files.
• Power outages.
• Hardware problems.
• Hardware driver problems.

There are several other reasons that may trigger Runtime Error r6034 that are beyond the scope of this article. Regardless of what triggers this error, it is crucial to ensure that it is fixed as soon as possible.

Further Information and Manual Repair

There are several ways to deal with Runtime Error r6034. However, one of the most effective ways is listed below as follows.

• When this error occurs, restart your computer. Make sure you press F8 before the windows logo is displayed.
• Choose safe mode and press enter.
• Go to the ‘Start’ button and type ‘msconfig’ in the search box. Press enter.
• The MSConfig program will now open.
• Choose ‘Start up’ in the general tab and then click on the ‘Load Start Up’ item.
• Click on the ‘Services’ tab. Now click ‘Hide all Microsoft Services’ and then choose ‘Disable All’.
• Close the system configuration window.
• Restart the computer.

After restarting your computer, you will notice that the Runtime Error r6034 has been removed. If this approach fails to deliver the desired results, it is advised to follow the steps listed below.

• Go to the start button. In the search box, type ‘System Restore’.
• When System Restore appears, click on it.
• The system restore window will open. Make sure any process or application that’s open is now closed.
• In the System Restore window, if a calendar list appears, it means the restore point is open. Now choose the point from where the error appeared and click Next.
• This process may take some time. Your system will restart automatically and the Runtime Error r6034 will disappear.

One of the most common ways cybercriminals use to inject suspicious code into devices is by tricking users into installing a malicious program on a targeted device. Oblivious users are vulnerable to such tricks, which is why Microsoft has been working hard in the background to address this issue. Recently, Microsoft announced the availability of a sandboxed version of Windows 10 that runs inside Windows 10 in order to isolate suspected software to run inside it and protect the system from potential threats. This Windows Sandbox feature is a new feature that keeps your computer secure. It is a virtual disposable environment that you can enable. So if suspect any software of being malicious, you can run this software in an environment and ensure that it won’t interfere with any normal processes and would not jeopardize files on your computer. To simply put it, “Windows Sandbox is a new lightweight desktop environment tailored for safely running applications in isolation”. So if the Sandbox is closed, all the residual files, software, and other data are deleted permanently. To enable Windows Sandbox, refer to the instructions provided below. Step 1: You have to make sure that you are running either Windows 10 Enterprise Editions or Windows 10 Pro and that your computer is running build 18305 or newer. Step 2: After that, you have to enable Virtualization to let another instance of Windows 10 running in Sandbox mode. Step 3: Next, search for Windows Features on and off in the search box and then select the appropriate entry. Step 4: From the list, go to the mini window and check the Windows Sandbox and then click on OK. Step 5: Afterwards, in the Cortana Search box, search for “Windows Sandbox” and select the related entry to run it in an elevated window. Step 6: Then from your main computer (host), copy the executable file and paste it inside the Windows Sandbox environment. Step 7: Now run the executable file in the Sandbox environment and use it as you normally do. Step 8: Once you’re done, close the Windows Sandbox application and as mentioned, every data regarding the executable file and the temporary environment will be deleted. Step 9: And for the sake of safety, ensure that there are no modifications made to the host because of the executions in the Sandbox environment. You have the option to contact Microsoft for feedback related to Windows Sandbox. You can use the traditional Feedback Hub if you have any suggestions or any issues. Just fill in the appropriate details and select Windows Sandbox for the feature category under the Security and Privacy section. And if you have any issues related to the execution of and within Windows Sandbox, simply choose “Recreate my problem” then select Start capture to reproduce the issue, and once you’re done, select Stop capture.

Error 0X800F080C is tied to corrupted system files and .NET framework issues. In this article, we will focus on how to fix it starting first with .NET fixes and then moving to system-related ones. Follow the guide step by step so you can fix this error fast and easily.

.NET issues

As previously stated 0X800F080C error can occur due to issues with .NET framework, 3.5 framework to be more precise and there are two ways we can fix this error. Follow the guide below as presented:

1. Install .NET 3.5 framework from Windows features

   First thing is to try and install the framework from Window features itself. Sometimes installation and activation of .NET 3.5 in other ways can result in this error. To install it do the following: Press ⊞ WINDOWS + R to open the run dialog Inside run type in appwiz.cpl and press ENTER to open up the Programs and Features menu Inside the Programs and Features menu click on Turn Windows features on or off. Check the box associated with .NET Framework 3.5 (this package includes .NET 2.0 and 3.0) Press OK Click on YES and wait for the package to be installed then reboot your PC

2. Run the .NET Repair Tool

   If the previous step was not successful or you already had .NET 3.5 installed then run the troubleshooter in order to fix issues. Go to the official Microsoft .NET framework repair tool website here and download it. Once downloaded install the tool and follow onscreen instructions.

Corrupted system files

If the previous solution has not provided you with results then you have system file corruption that needs to be fixed. Move from one solution to another as presented below:

1. Run SFC scan

   SFC scan is a built-in Windows tool for solving corrupted system files issues, it is fully automated and does not require from the user any kind of knowledge or information. To run it and scan the system do the following: Press ⊞ WINDOWS + X to open the secret menu Left-click on the command prompt (admin) In command prompt type SFC /SCANNOW and press ENTER Wait for the process to finish, do not interrupt it and once it is done, restart your computer

2. Run DISM scan

   DISM scan is similar to SFC scan but it tackles different types of system file corruption and it is recommended to run it also after SFC has been completed. Please note that for DISM scan to be successful you will need a stable internet connection since DISM will replace corrupted files with new ones downloaded from Microsoft. To run it do the following: Press ⊞ WINDOWS + X to open the secret menu Left-click on the command prompt (admin) inside command prompt type: exe /online /cleanup-image /scanhealth followed by ENTER, then type: Dism.exe /online /cleanup-image /restorehealth also followed with ENTER. Leave scan to finish and reboot your PC

Each time we turn ON our computer or wake it from hibernation we are greeted with a Windows login screen where we need to provide login credentials in order to get into Windows itself and start working. This method of preserving data and privacy is perfectly fine and as a matter of fact, it is recommended for mobile computers but if you have a home computer in a safe environment where no one will try to look at your data or rummage through your personal stuff then removing login screen is safe enough action and can cause you a lot piece, from time-saving to less frustration on every restart or sleep action. In previous Windows versions, it was much easier to turn off this feature but it seems Microsoft has determined that our privacy and security are important and somewhat removed the ability to turn OFF the lock screen. In this guide, we will show you how you can still remove the lock screen and automatically log in with your account like in the good old days. The first thing you need to do is to press ⊞ WINDOWS + R  to bring up the Run dialog In the dialog, type in netplwiz and press ENTER. You will find yourself in the User Accounts window, inside deselect Users must enter a user name and password to use this computer. Press OK Sign in the window will pop up where you will have to type in your password and confirm it in order to start the feature. After typing in your password and confirming it, press OK. That's it, next time you wake your computer from hibernation or turn it ON, you will automatically be greeted with a desktop instead of a Windows login screen.

What Is 0x80004001 Error Code?

0x80004001 is an error code that Windows users encounter quite commonly.

This error usually occurs when users try to update an old Windows application or attempt to run a certain application. When this error appears on the screen, the system automatically restarts to stop further processing. The error results in a blue screen after the system boots.

This blue screen is known as the Blue Screen of Death.

Error Causes

There are different files in the Windows operating system responsible for its smooth functioning. Sometimes problems like viruses or incorrect register entries corrupt or damage these files. This is when this 0x80004001 error appears.

Simply put, some of the most common causes that trigger 0x80004001 error are listed below as follows.

• Corrupt or damaged EXE, VXD, DLL files of Windows
• Incorrect entry of registry files
• Presence of viruses or malware in the system
• Corrupt or damaged system files
• Unfinished application installation

Irrespective of what causes this error, it is of utmost importance to troubleshoot it as soon as possible.

Further Information and Manual Repair

While there are several ways of troubleshooting this error, the two most useful approaches have been listed below as follows.

• This solution is for advanced users. Start your system and log on to it as the administrator. Click on the Start button. Now select All Programs->Accessories->System Tools. Finally, click on System Restore. In a new window, select the option “Restore My Computer to an Earlier Time”. Now click on Next. A list of restore points will be displayed. Choose the most recent restore point from this list and click “Next”. Now click next on the confirmation Window again. Once the restoration is finished, the computer will restart itself and you will observe that the error no longer appears.
• This solution is for beginner or novice users. Download a 0x80004001 error repair utility available online. Install this program on your computer and use it to scan for the error in your system. When the scan completes, find if any feature allows you to fix errors. If yes, click on it. Now restart your computer again. You will notice that the virus has disappeared. It is a good idea to use error repair utilities because they scan the system, diagnose the error and then perform the repair.

Use any of the methods listed above to get rid of the 0x80004001 error once and for all.

Microsoft has been bringing new lock-screen features with every iterative feature release of Windows 10 in order to improve user experience. However, Windows 10 users have different opinions regarding it. Some users are pleased with it while some users simply do not like it. So if you are one of the users who seem to not approve of this feature, read on as this post will be about enabling or disabling the Console Mode sign-in feature in Windows 10. Before you proceed, take note that you will not be able to use your mouse pointer in this Consol Mode login screen and you can only use your keyboard to navigate around various options. You might also want to create a System Restore point just in case. To enable or disable the Console Mode sign-in in your Windows 10 computer, refer to the given steps below. Step 1: Tap the Win + R keys to open the Run dialog box. Step 2: Then type in “Regedit” in the field and tap Enter to open the Registry Editor. Step 3: Next, navigate to the following registry path:

ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionAuthenticationLogonUITestHooks

Step 4: From there, look for a DWORD named “ConsoleMode”. If you don’t see this DWORD, you can just create a new DWORD and name it as “ConsoleMode” and make sure that its base is set to Hexadecimal. Step 5: After that, double click on ConsoleMode and change its value to “0” to disable it and “1” to enable it. Step 6: Now restart your computer to apply the changes made. Like pointed out, you can only use your keyboard when you’re in the Console Mode login window or screen. You can just use the ESC button to go back to the menu while you can utilize the arrow keys so you can go through the options that are mostly vertically arranged and the Enter key to select an option. In the Console Mode, sign-in using the Passwords and PINs worked efficiently.

Windows 11 has been officially presented during Microsoft’s virtual event on June 24^th. Since presentation internet has been pretty live and busy with a discussion about it, some discussions are positive, some not so much but that is expected and it happens always when a new product is presented. One of information that we have about Windows 11 is tied to the home edition of this OS, Windows 11 home edition will require an internet connection at setup, and a Microsoft account in order to be installed and used. Previous versions of Windows could be installed and used with local accounts but it seems Microsoft has abandoned that idea for its new OS. OS will be delivered mostly as updates or via internet download so internet and online requirement make sense but why it cannot use the local account and must have a Microsoft one is beyond me.