Sticky Notes is one of the useful programs and in the early days, the option is available for users to change the font size of the text a lot easier. However, for some unknown reason, Microsoft decided to get rid of this feature in the latest Windows Update. One would expect that the feature will be replaced by an even more useful feature but it’s not which makes the Sticky Notes app worse than before. Worry not though for it doesn’t have to stay that way as there is another thing you can try to change the font size in your Sticky Notes app and that’s what we’re going to cover in this post. As mentioned, Microsoft removing this font feature is quite strange and in the past, users asked for this feature and since it’s no longer available, you can try following the steps given below to bring it back. And for that, you need to go to the Ease of Access section in the Settings app. Refer to the steps given below for more instructions. Step 1: First, tap the Win + I keys to open Settings and then go to the Ease of Access section. Step 2: After going to the Ease of Access menu and select Display from the list of options. Step 3: From there, you should see an option that says “Make text bigger”. And then use your mouse to navigate to the slider to change the size of the font. Note: Take note that after doing all the steps above, it will change not just the Sticky Notes app but also everything in Windows 10. This method is actually the best since it only changes the size of the apps rather than a wholesale change in your Windows 10 computer. Step 4: Next, scroll under Display until you see the “Change the size of apps and text on the main display” option where you’ll see that the option is 100% but you’ll want to change that to 125%. Step 5: After that, click on the drop-down menu and select 125% and then restart your Windows 10 computer. Step 6: Now open the Sticky Notes app and check if you can now change the font size in the Sticky Notes app.

The latest security vulnerability was discovered inside both Windows 10 and Windows 11 letting any user access admin privileges inside the operating system. This can, of course, be used by a potential attacker to get full control of the system. The problem lies in Microsoft's security rules assigned to the Windows Registry and the Security Account Manager. Both for some reason have reduced restrictions allowing any local user to fully access the files without administrator privileges. The problem is even more amplified if we think about Security Account Manager which includes all account data including the passwords of all users using the same PC. This can provide a potential attacker with all information and let them log on into the administrator account for full control. Microsoft is aware of the matter and is tracking it with code CVE-2021-36934, and includes a complete workaround for the issue, which includes restricting access to  %windir%\system32\config and deleting any restore points or Shadow volumes that were created before that point until the hole is plugged with an official security patch.

There are times when the WMI Repository gets corrupted which results in the Provider Load Failure. To resolve this issue, you need to repair or rebuild the WMI Repository in your Windows 10 computer. In this post, you will be guided on how exactly you can do that. In case you don’t know, the WMI which stands for Windows Management Instrumentation is a set of specifications from Microsoft to consolidate the management of devices and applications in a network. The WMI is a database that stores meta-information and definitions for WMI classes. Using only these, the conditions of the systems can be known. You can find the WMI Repository in %windir%System32WbemRepository. It provides end-users with the status of the local or remote computer system. Keep in mind that you must not use this on the Server 2012 Cluster machine. Although there are command-line tools that can fix or restore the Windows Management Instrumentation repository. However, Microsoft suggests that it’s better if you verify if there is corruption. Here are a list of errors as well as permission issues you might encounter:

• Unable to connect to root default or rootcimv2 namespaces. It fails with the error code “0x80041002” pointing to “WBEM_E_NOT_FOUND.”
• 0x80041010 WBEM_E_INVALID_CLASS
• When you open Computer Management and Right Click on Computer Management (Local) and select Properties, you get the following error: “ WMI: Not Found” or it hangs trying to connect
• Trying to use wbemtest , and it hangs
• Schemas/Objects missing
• Strange connection/operation errors (0x8007054e)

To verify if there is corruption, you can try running the following command in an elevated Command Prompt:

winmgmt /verifyrepository

 After you enter the command, if there is a response saying, “repository is not consistent”, then the repository has an issue. If not, then something else is causing the problem. Since you are certain that corruption exists in the WMI repository, then here are some suggestions you need to check out to repair or rebuild the WMI repository.

Option 1 – Try to reset WMI Repository

• Type “command prompt” in the Start Search and right-click on Command Prompt from the search results and then select “Run as administrator”.
• After opening Command Prompt with admin privileges, type and enter this command: winmmgmt /salvagerepository

The command you entered is used when the winmmgmt command performs a consistency check. So if an inconsistency is detected, it will rebuild the repository.

• Next, execute this command to see if the WMI repository now comes back as consistent: winmgmt /verifyrepository

This command will perform a consistency check on the WMI repository.

• If it states that the WMI repository is not consistent, then you need to type and enter this command: winmgmt /resetrepository

This command is used to reset the repository to its initial state when the operating system was first installed.

Option 2 – Try to force recover the WMI Repository

The WMI Repository comes with a built-in self-recovery process so when the WMI service restarts or detects any corruption, it will automatically trigger the self-recovery procedure. This can happen in two ways:

• AutoRestore: This will use the backup images if the Volume Shadow copy or VSS backup is turned on.
• AutoRecovery: The rebuilding process will generate fresh images of the WMI repository based on the registered MOFs. The MOFs are available in the registry located at HKLMSoftwareMicrosoftWBEMCIMOM: Autorecover MOFs

Note: Autorecover MOFs is a key so double click on it to check its value. On the other hand, if the self-recovery procedure does not work, you can try to use the force-recovery process instead. How? Refer to these steps:

• First, you need to check the reg key value is empty or not under this registry path: HKLMSoftwareMicrosoftWBEMCIMOMAutorecover MOFs
• If the reg key value is empty, you have to copy-paste the reg key value from another computer. Just make sure that it’s from the System which is equivalent to the computer in question.
• Next, type and enter this command: Winmgmt /resetrepository
• After you enter the command, if you get an error that says, “WMI repository reset failed. Error code:0x8007041B. Facility: Win32”, then you have to stop all the Dependency Services on the WMI service by running the following commands:
  • net stop winmgmt /y
  • Winmgmt /resetrepository

This should fix the problem.

There are times when you may find it hard to kill a particular process in the Windows Task Manager and every time you try to do so, you will only get an error message saying, “Unable to terminate the process, The operation could not be completed, Access is denied”. If you are one of the users who is constantly getting this error, read on as this post will provide you with a couple of options you can try to resolve the problem. Refer to the given instructions below if you are unable to terminate a process in the Task Manager but before you proceed you need to restart your PC and then try killing the process again, if you’re still not able to do it, you need to follow the options laid out below.

Option 1 – Try using Taskkill

• Open the Command Prompt as admin from the WinX Menu.
• After opening Command Prompt, type in the following command and tap Enter to execute it:

taskkill /IM "processname" /T /F processname – it is the name of the process which you can see on the Details tab of the Windows Task Manager. /IM – it is the one that specifies the image name of the process, which follows, that is to be terminated. /T – it is the one that kills not just the main process but also the child process. /F – it is the one that terminates the process forcefully.

Option 2 – Try using the WMIC

• Open Command Prompt as admin from the WinX Menu.
• From the Command Prompt window that opens, type in the following command and hit Enter to execute it:

wmic process where name='processname.exe' delete

Note: In the given command, you need to replace “processname.exe” with the name of the particular process you want to terminate which is found in the Details tab of the Windows Task Manager.

Option 3 – Try using PowerShell

• The first thing you have to do is open an elevated PowerShell prompt.
• From there, type in the following command and hit Enter to execute it:

kill -id pid

Note: In the given command above, “pid” is the Process ID number of the process you want to terminate. And for you to identify this number, you need to open the Details tab of the Windows Task Manager once again and take note of the number against the process you want to get rid of. Alternatively, you can also run the following command in the PowerShell prompt that you’ve pulled up to get the process ID number:

Get-Process

For example, “5364” is the process ID number for the DimScreen.exe process which is the process you want to terminate. In order for you to kill this process, you need to type in this command:

kill -id 5364

As you know, the Microsoft store is a built-in tool in Windows 10 where you can find a variety of applications. It helps users in downloading or updating apps in the system. However, there are instances when you could encounter issues while using it. One of the issues that you could face when using the Microsoft Store app is when it keeps on offering apps you have just updated or when you are not able to update any apps at all. This kind of issue in the Microsoft Store app might be caused by other issues like a damaged Windows Store cache. There are several options you can check out to resolve the problem. You can try to check the registry setting or run the Windows Store apps troubleshooter or clear the Windows Store cache manually or reset its settings. You could also try to re-register the Microsoft Store app. For more details, refer to each one of the options provided below but before you troubleshoot the problem, make sure that you create a System Restore point.

Option 1 – Run the Windows Store App troubleshooter

The Windows 10 Store Apps Troubleshooter will help you in fixing the problem in Microsoft Store. This is a great built-in tool from Microsoft that helps users fix any app issues. To use the Windows Store Apps Troubleshooter, follow the steps below.

• Tap Win + I keys again to open the Windows Settings panel.
• Go to Update & Security and then go to Troubleshoot.
• Under the Troubleshoot section, on your left-hand side, scroll down to find Window Store Apps.
• Then click on the Run the troubleshooter option and follow the on-screen instructions and then see if it fixes the problem.

Option 2 – Try checking the settings in the Windows Registry

The next thing you can do to fix the problem is to check the Registry settings for the Windows Store.

• Tap the Win + R keys to open the Run utility and type “Regedit” in the field and then hit Enter to open the Registry Editor.
• Next, navigate to this registry path: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionCurrentVersion
• From there, look for the DWORD named “CurrentVersion” and make sure that its value data is set to 6.3, but if it’s not then change its value data to 6.3
• Exit the Registry Editor and restart your computer and then see if it fixed the problem with the Microsoft Store app.

Option 3 – Try to reset the Microsoft Store cache

Just like browsers, Microsoft Store also caches as you view apps and games so it is most likely that the cache is no longer valid and must be removed. To do so, follow the steps below.

• Right-click on the start button and click on Command Prompt (administrator).
• Next, type in the command, “exe” and tap Enter. Once you do, the command will clear the cache for the Windows Store app.
• Now restart your PC and afterward, try opening Microsoft Store again and then try to install your app or update your computer again.

Option 4 – Try to re-register the Microsoft Store app via Windows PowerShell

• Tap the Win + X key combination or right-click on the Start button and click on the Windows PowerShell (Admin) option.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed and open the Windows PowerShell window.
• Next, type in or copy-paste the following command to re-register the Microsoft Store app and tap Enter:

powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRootWinStoreAppxManifest.xml

• Wait for the process to be completed and then restart your computer.

OneXPlayer is a direct competitor to Valve’s upcoming steam deck. This device is clearly inspired by Valve’s offering and it shows all over the place, from its looks to its purpose and aims to PC gamers as a handheld device.

Hardware under the hood

This device is packing a 7-inch 1080p display, 11th generation Intel Core i7-1195G7 CPU, stunning 16GB of RAM, 512GB SSD drive with the option to purchase 1TB or 2TB model. GPU of choice is Intel iris Xe Graphics that is in our opinion a bottleneck in the whole system and for more demanding games, we believe switching them to 720p would be a better option. Everything here is powered with a 10455 mAh lithium-ion battery.

OneXPlayer inputs and other stuff

Handheld is equipped with dual bumpers and dual linear triggers. The console comes with dual speakers on both sides of it. Inside the console, there is an aluminum heat sink with copper heat pipes and a fan in order to cool internal hardware. On the outside, we have two USB-C ports and one USB-A port for connections, and of course, a headphone jack for headphones. The console comes with Wi-Fi 6 and Bluetooth 5.0 for wireless connectivity.

Price

The base entry model will cost you a whopping $1.259, 1TB model $1.399 and 2TB one will go as far as $1,599. With this kind of price, I am not sure it can come up as a winner against Valve. Sure it is packing fully licensed Windows 11 that will for sure offer more options than Stem’s OS based on Linux but even with that advantage I do not think it justifies such a big price difference.

Conclusion

Of course, this kind of console or handheld PC will still find its customer base, many users will probably like it since it comes Windows ready out of the box. Sure, you can place Windows on Steam deck as well but you will need to know how, where everything is ready and you can run beside steam other launchers without issues like origin, uplay, gog, etc. How this will be accepted by community time will tell but it is good to see that there is variety and competition in handheld PC space.

Disk cleanup is part of Windows 10 tools and it is essential in keeping your computer up and running in optimal settings and to free so much needed space as well as remove temporary files that can accumulate over time. Using disk cleanup from time to time is recommended and a very useful habit that will save you some headaches and optimize your computer running time, speed up boot sequence, etc. Think of it like cleaning up your desk, from time to time it can get too overwhelmed with junk and non-important things and if you are keeping it tidy all the time each time you need to find something it will be much faster and easier, same goes with computers, so if you do not have it, try to develop a habit that once per month you start disk clean up and remove trash from your hard drive. In order to do so, press ⊞ WINDOWS + E to bring File Explorer up Once File Explorer is up and running right-click on the hard drive you wish to run disk cleanup on and click on properties. Properties Windows will open on the general tab, on that tab you have disk cleanup on the lower right part of properties, click on it. Wait for Windows to gather information about your hard drive and files on it. After it is finished you will be greeted with the next screen: Here you can thick and mark which items you would like to get rid of and which ones you would like to keep. Note that you can freely tick all of them and remove them since removing these files will not break WIndows in any way. make your choices and click on ok. You can also click on Clean up system files to run system files cleaner and get rid of junk there, you will not be able to choose any options there, Windows will alone clean up what is not needed. After disk cleanup is finished least thing you will have is more free disk space, but like mentioned, keeping your Windows and computer healthy goes a long way in its usability, speed, and performance.

A lot of users prefer to use Microsoft OneDrive when it comes down to cloud storage as it does not only come with the seal of approval from Microsoft but it’s also primarily good and better compared to other cloud storage services. However, that doesn’t mean that OneDrive isn’t without any issues. For one, you might encounter an issue where the OneDrive thumbnails do not show in File Explorer in Windows 10. If you are currently experiencing this problem, read on as this post will help you fix it. As you know, you can add OneDrive to your Windows 10 computer and have all the files locally synchronize to the cloud and so on. This means that whatever is available in the cloud will be seen on your computer. It is smooth and definitely saves you a lot of time which is why a lot of users prefer to use it. So if you suddenly not see any thumbnails in OneDrive, then that would be a problem. You are actually not the only one having this problem as there are other users who reported getting the same issue recently about the picture thumbnails that no longer show up in the OneDrive folders in the File Explorer. At the time of writing, it isn’t clear yet what the cause of the issue really is. Even so, there are still potential fixes you can check out to resolve it, and the sooner you do it, the better as this can be a major problem. To get started, refer to the instructions given below.

Option 1 – Try to disable Files on Demand

The first thing you can do to fix the problem is to disable the Files on Demand. This is what you have to do to get things under control.

• First, right-click on the OneDrive icon located in the taskbar and go-to of OneDrive.
• After that, click on More and Settings. This will open a new window where you have to click on the Settings tab and uncheck the “Files on Demand” service.
• Once done, restart your computer and check if you can now see the thumbnails in the OneDrive folder. However, if it didn’t work, then proceed to the next given option below.

Option 2 – Try to change the icon view

The next thing you can do to fix the problem is to change the icon view. It is possible that the problem might have something to do with the size of the icons than anything else. So you have to change the icon view and to do that, follow these steps:

• First, open Control Panel in Windows 10.
• Next, in the search box, type “folder” and then click on the File Explorer Options.
• From there, click on the View tab and uncheck the “Always show icons” option, and make sure that showing thumbnails is active.
• Now go back to Control Panel and type “system” in the search box. This will open a new window where you have to select the “View advanced system settings” option.
• Then under the Performance section, click on Settings and click on the option that allows you to show the thumbnails instead of icons.

Website breaches and stealing user data is nothing new in the world of the internet. Although a very unpleasant experience it still happens even on some high-quality websites. In this article, we will not focus on how can you not be the target of this kind of attack, because you really cannot. Weel you can kind of if you decide not to have your data on websites at all, but let's just say that is not something you are willing to do.

So, in this case, you have some social, forum, or gaming accounts but you heard that service has been breached and that your email or password might be stolen. Well in this case all you need to do is of course to login into the service and change your password. But, what happens if you are not aware at all that service has been compromised?

Mozilla foundation has asked themselves this same question it seems and they have decided to help us out. They have placed a free online service where you can just by typing in your email address find out if your email or data has been compromised in any way.

Go to https://monitor.firefox.com/ and check it out, if you find out that there is some website that you did not know was breached, change your password right away, and if you have used the same password for anything else (I hope not), change them as well.

One of the most useful and powerful built-in utility in Windows 10 is the DISM tool. This tool can be used with the Command Prompt command line as well as for other purposes. However, it is not without flaws and there are times when you may encounter some issues while using it. One of the problems you can get while using the DISM tool is the following error:

“The scratch directory size might be insufficient to perform this operation”

This kind of error in DISM occurs when the DISM command is executed from the Windows Recovery Environment due to the limited size permissions of a delivery where the operating is being performed. To fix this DISM error, you need to follow the instructions laid out below. Step 1: First, tap the Win + R keys to open the Run utility and then type “cmd” in the field and tap Enter to open Command Prompt. Step 2: Next, you have to specify a scratch directory that contains the Windows folder and to do that, you can either use the DIR command or the BCEDIT command. So in the elevated command prompt type and enter “dir” or “bcedit”. Step 3: After that, you will see a list of folders inside the C: partition. Now you have to create a folder named “scratch” inside the partition. To do so, execute the following command:

mkdir C:Scratch

Note: The command you just entered will create a directory inside the root of the C: partition named Scratch. Step 4: Now that you’ve created the Scratch folder, note that each time you run any of the DISM commands, you have to enter the following code snippet in them:

/ScratchDir:C:Scratch

 Note: For instance, if you are using the DISM tool to repair the offline Windows image, instead of executing the “Dism /Online /Cleanup-Image /RestoreHealth” command, you now have to execute the “DISM /Image:C: /ScratchDir:C: Scratch /Cleanup-Image /Restorehealth” command. And if you want to remove a selected installed update package, you can use the “DISM /image:C: /ScratchDir:C:Scratch /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e75~amd64~~16299.196.4.9” command. Keep in mind that the mentioned package is only an example. And lastly, you also have to replace the drive letter in the new code snippet when you execute the commands given above.