Increase your Internet Speed in Windows 10

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.

If your Windows PC encounters an error, it will display a Blue Screen of Death or BSOD error which usually comes up for a fraction of second and creates some logs or Dumps Files as what other user prefers to call it and then boots your PC suddenly. This process usually takes place quickly that most users find it hard to get the error code and won’t probably be able to check what really went wrong with their PCs. This is where the dump files come in. They are stored internally in your computer and can only be accessed by an administrator. They are classified into 4 main types and in Windows 10 they are either:

1. Complete Memory Dump
2. Kernel Memory Dump
3. Small Memory Dump (256 KB)
4. Active Memory Dumps

Dump Files are useful as they could help you in resolving the problem and so you need to configure your Windows 10 PC to create them but first, you need to make a system restore point. This is essential as you are about to modify some system files as well as critical Windows 10 settings. There are two ways you can create Dump files – first is by modifying the settings in the Startup and Recovery and lastly is via the WMIC command line. Refer to the instructions prepared below to be guided on how you can create Dump files after any BSOD error using these options.

Option 1 – via Startup and Recovery

• Type in “control panel” in the Cortana Search box and then click on Control Panel from the search results to open it.
• After opening Control Panel, you need to make sure that you view the contents by their Category then click on the header link which is labeled “System and Security” or you could also right-click on the This PC icon and then click on Properties.
• Next, select the Advanced system settings from the left panel. Once you do, a new and small window will pop up.
• Under the newly opened window, look for the section called Startup and Recovery and then click on the Settings button.
• And from the System Failure section, you can choose any option from the drop-down for Write debugging information such as:
  • None – this means that there is no dump file created by Windows
  • Small Memory Dump – this means that Windows will create a Minidump file on BSOD
  • Complete Memory Dump – this means that Windows will create a Complete Memory Dump file on BSOD
  • Automatic Memory Dump – this means that Windows will create an Automatic Memory Dump file on BSOD
  • Active Memory Dump – this means that Windows will create an Active Memory Dump file on BSOD

Note: The complete dump needs a page file that is allowed to be the size of the physical memory installed in your PC with a dedicated 1 MB of space for just the page header.

• Now once you have selected the most suitable option for you, just click on OK/Apply and then exit.
• Restart your PC to successfully apply the changes made.

Option 2 – via the WMIC command line

• The first thing you need to do to create Dump files via the WMIC command line is to tap the Win + X keys combination or simply right-click on the Start button and then select the Command Prompt (Admin) option. You could also type in “cmd” in the Cortana search box and then right-click on Command Prompt from the results and select Run as administrator.
• After that, type in any of the commands given below depending on your preferences so that your Windows 10 PC will be configured to create Dump Files:
  • No dump file: wmic RECOVEROS set DebugInfoType = 0
  • Small Memory Dump: wmic RECOVEROS set DebugInfoType = 3
  • Kernel Memory Dump: wmic RECOVEROS set DebugInfoType = 2
  • Complete Memory Dump: wmic RECOVEROS set DebugInfoType = 1
  • Automatic Memory Dump: wmic RECOVEROS set DebugInfoType = 7
  • Active Memory Dump: wmic RECOVEROS set DebugInfoType = 1

Note: A complete dump has to have a Page file which is allowed to be the size of the physical memory installed on your PC accompanied by a 1 MB space for just the page header.

• Now type in “exit” in the Command Prompt to exit it.
• Restart your PC to apply the changes made successfully.

You have the option to choose to configure the Network to Private or Public when you set it on Windows 10 PC. On the other hand, if the option to change the Network from Public to Private goes missing in Windows Settings then this post will surely help. You can find this setting under Settings > Network and Internet > Ethernet and appears when you click on it. If you are not able to see the option to change the network profile, then you either can’t open the settings, or the option to change it has been disabled. To resolve this issue, you can either use the Registry Editor or Windows PowerShell. Refer to the options given below for more details.

Option 1 – Change the Network Profile via Registry Editor

Changing the Network Profile can be done using the Registry Editor. But before you proceed, make sure that you create a System Restore Point first just in case. Refer to the steps below to do so.

• Tap the Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and hit Enter to open the Registry Editor.
• After that, navigate to this key: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionNetworkListProfiles
• Now expand the Profiles key folder located in the left pane to see one or more folders.
• Next, expand each one of these folders and look for the “Description” sub-key which should match the name of your network.
• After you find the Description sub-key, look for another sub-key named “Category” and double click on it to open it.
• Now change its value from “0” to “1” to change the Network Profile from Public to Private.

Option 2 – Change the Network Profile via Windows PowerShell

Aside from the Windows Registry, you can also use Windows PowerShell in changing the Network Profile from Public to Private and so on. Take note that you have to use PowerShell with admin privileges. Just refer to the steps below to do so.

• Tap the Win + X keys and then select the “PowerShell (Admin)” option.
• Next, click on Yes if the User Account Control prompt appears.
• After that, execute the commands listed below. Hit Enter right after you key in each one of them.
  • Get-NetConnectionProfile
  • Set-NetConnectionProfile -InterfaceIndex <index number> -NetworkCategory Private

Note: Since every Network Profile has an index number, you can check the label “Name” to identify the network that you want to change.

The Event Viewer in the Windows operating system is used to troubleshoot any computer issues. It is one of the most useful tools that keep logs of both security and system events. It also monitors for both software and hardware problems in the computer. This tool is the only one with amazing features that maintain logs about everything that’s going on in the computer system. It keeps track of all the information to the point where going over them will take a lot of time. Luckily, the Event Viewer tool now allows users to create custom views where you can set the filters and sort the data recorded to limit the information details to only what you’re interested in seeing. For instance, if you want to troubleshoot with one hard drive, you can just create a special custom view to display only the hard drive warnings in the security logs. This will save you hassle and time. Take note that the logs in the Event Viewer are divided into two main categories namely the Window logs and the Application and Services logs. You can just set the filter to the logs by their event id, specific date, and many other events when you have to troubleshoot some problem in your computer. So if you are trying to troubleshoot a problem in your Windows 10 computer and you’re checking the Event Viewer, read on as this post will guide you in creating custom event views in the Event Viewer. To get started, refer to the instructions given below. Step 1: Go to the Start menu and in the search box, type “event viewer” and then click on Event Viewer from the search results to open it. Step 2: After opening Event Viewer, click on Custom Views located in the left pane of the window. Step 3: Next, click on the Administrative events under the Custom View to create special log views. Step 4: Then on the right side of the window, click on Create Custom View to open the Create Custom View window. Step 5: There is a logged drop-down list under Filter. From there, you have the option to choose an appropriate predefined time or use a custom time range for your Custom log views. Step 6: After that, select an appropriate event level for your custom view. You have fine entry-level options to choose from such as critical event level, error, warning, information and verbose.

• Critical – select this if you want to see the events that require your immediate attention in the custom view.
• Error – select this if you want your Event Viewer to display the events that are less critical but hints at the problems.
• Warning – select this event-level if you want to see the event with the potential problem but may not bound to happen.
• Verbose – select this if you want to see detailed information about all the events.

Step 7: After you’ve selected the event level, you now have to select how you want the events to be filtered. They can either be filtered By the log or By the source.

• By the log – you can select two options called Windows log and, Application and Service logs. The Windows logs allow you to filter the logs created during events like setup, security, applications, and system events. While the Application and Service logs filter the log created by the installed applications in your system.
• By the source – select this if you want your Custom View to search for information in event sources. It allows you to view events in detail for various applications and devices.

Note: You have the option to further customize the event logs with more filters like Event IDs, task category, keywords, User, and Computer. Using these additional filters, you can choose to filter the events in the special views by specifying event id numbers in the Event IDs, entering predefined Windows words in the Keyword, specify the user accounts in the User field, as well as choose the system from the server to maintain logs in the Computer field. Step 8: Once you’re done customizing the log filter, click on OK to apply the changes made. Step 9: After that, a Save Filter should be displayed in the Custom View window. Just enter the Custom View name and select the Event Viewer folder where you want to save the Custom view. The folder name should be Custom View by default. And if you want, you can also create your own folder if you want your custom views to be visible to all the system users. Step 10: Next, check all the Users box located in the lower corner of the window and then click the OK button after you’re done. You should now see the customized filter you just created on the left side of the window. Just click on it to check your filtered events in the center of the Event Viewer window. And for you to save the custom view logs, simply right-click on the Custom views you created and then click on Save All Events in the Custom View As from the drop-down menu. Then put a name on the file and select the appropriate location where you want to save the logs and click on the Save button. Note that the log file is saved with the “.EVTX” file extension and when you double click on it, it will open the file in the Event Viewer.

The use of Biometrics is supported by Windows 10. Aside from that, it also supports PIN, password, picture password on all computers and if your computer has the proper hardware, Windows 10 also supports facial scanning, iris scanning, and even fingerprint scanning. You can see all these exciting features inside Settings > Accounts > Sign In Options. On the other hand, you can’t really expect to make use of all the above-mentioned features since it depends if the hardware is available to support them. One of the most interesting features is the use of Biometrics which is really useful in workplaces and so this post will show you how you can enable or disable the Domain Users Sign In on Windows 10 using Biometrics via Registry Editor or Group Policy Editor. But before you go on, you need to create a System Restore Point first since the modifications you’re about to do might affect the functioning of your computer. So in case something went wrong, you can always undo the changes you’ve made.

Option 1 – via Registry Editor

• Tap the Win + R keys to open the Run dialog box.
• Next, type “Regedit” in the field and hit Enter to open the Registry Editor.
• After that, navigate to the following registry path:

HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftBiometricsCredential Provider

• From there, right-click on the right-side panel and click on New > DWORD (32-bit) Value.
• And then set the name of the newly created DWORD as “Domain Accounts”.
• Afterward, click on “Domain Accounts” and set its value to “1”. This will allow the domain users to sign in to Windows 10 using Biometrics. While the value of 0 will disable the domain users sign in to Windows 10 using Biometrics.
• Exit the Registry Editor and restart your computer for the changes to take effect.

Option 2 – via Group Policy Editor

• Tap the Win + R keys to open the Run dialog box.
• Next, type “gpedit.msc” in the field and hit Enter to open the Group Policy Editor.
• After that, navigate to the following setting:

Computer Configuration > Administrative Templates > Windows Components > Biometrics

• Then double click on the following entries located on the right-side panel and set the radio button to Enabled on all of them.
  • Allow the use of Biometrics.
  • Allow users to log on using Biometrics.
  • Allow domain users to log on using biometrics.
• Now exit the Group Policy Editor and restart your computer to apply the changes made properly.

Computer voice control has moved a long way from its beginning routes and in today's age controlling your PC with voice is truly a reality and fully possible. Voice control is taking up the steam in everyday life, from simple commands in cars, Alexa, smartphones, TVs, etc. to modern computers.

Windows 10 has introduced voice control into PC with Cortana even during the installation process but a lot has changed from having a virtual assistant in begging days and in today's modern Windows 11 OS. You can now freely open apps, move, copy delete files, and even dictate in order to create a word document.

However, in order to take this advantage, you will need to turn it off first since it is disabled by default. Of course, you will need a microphone and some spare time to train Windows in understanding you properly.

Setting up Voice Control

Just like in Windows 10, in Windows 11 voice control is also in accessibility options and the first step is to turn ON Windows Speech Recognition.

Click on the Start button and type Settings into the search bar, click on Open, or press ENTER. On the left side of the settings, window locate and click on Accessibility. On the right part once Accessibility is selected scroll down and find a section titled Interaction and click on Speech. Turn on the switch next to Windows Speech Recognition.

A pop-up will appear that will lead you through the rest of the setup and that's it.

Improving Voice Control

In order to make your voice control better, if you are not satisfied with the results, you can sample more of your voice into the algorithm to tune it more to your liking. Sadly this option is still deep in Control Panel.

Click the Start button and type in Speech recognition into the search bar, look for the search result with Control Panel displayed under it, and click on Open. Click on Train Your Computer to Better Understand You and follow the instructions.

The process will probably take a few minutes. The more data you provide to the speech recognition model, the more accurate it will be when interpreting your instructions. You can train the model multiple times, and each time you do, it should improve the accuracy.

Error code 0x803f7000 -What is it?

Error code 0x803f7000 refers to an issue in Windows 10 with downloading apps through Windows Store. When you choose the app or game to download, it heads to Downloads in the Store app. Then it says it is acquiring a license but then fails. When you click the “See details” link, you see the error code 0x803F7000. It could mean that the date and time or region settings in your Windows 10 are incorrect or there are some problems with the Windows Store Cache.

Symptoms

• This error appears when you are running Windows 10 and trying to download an app through the Microsoft store. The error code may appear with this message: “Something went wrong. The error code is 0x803f7000, in case you need it”
• You might also see this message along with the error code: "It looks like you've reached your device limit for installing apps and games from the Store on your Windows 10 device. If you want to install apps and games from the Store on another Windows 10 device, remove a device from the device list."

Solution

Error Causes

There may be several reasons for this error:

1. This problem may arise if the date and time in Windows 10 are incorrect.
2. If the region has been set incorrectly.
3. Problems with Windows store cache.
4. Windows store server overloaded.
5. The Windows version you are using is pirated.

Further Information and Manual Repair

Method 1:

Correcting date and time:

• Open up Control Panel > Clock, Language, and Region.
• Then click on Date & Time.
• Now click on Change date & time to correct your time.

Method 2:

Correcting region:

• Navigate to Control Panel > Clock, Language, and Region.
• Then click on Region.
• Then click on the Location tab.
• Now set your actual region from Home location section.
• Click Apply & OK.

Method 3:

Resetting Windows Store:

• Press Windows Flag Key + X from your keyboard. Then select Command Prompt (Admin). It will launch Command prompt as administrator.
• Then type wsreset and hit Enter.
• Wait for a few seconds. It will automatically open Windows Store.
• Then try to download any apps.

Method 4:

1. Open Command prompt in local machine and type in the Windows Store reset tool exe
2. Activate Windows by going to Settings>Updates and Security
3. Run the Modern UI/metro app troubleshooter from Microsoft
4. Keep trying it several times.
5. Try changing locale and time zone to the United States as shown below
6. Go to control panel, Language settings
7. Select location to the United States
8. This will reset the language to US English. After this try downloading the apps again.
9. Try restarting the Windows Updater service or restart the machine once.

You must make sure that you have a good internet connection. You need that for the updates and downloads complete without disruption.

Method 5:

Make sure the app isn’t blocked by the Windows firewall: To make your PC more secure, some apps are blocked by Windows Firewall by default. For proper functioning, you might need to enable an app to receive info through the firewall. For more info, see the "Allow an app to receive info through the firewall," and follow the procedure from start to finish.

Method 6:

Check with your system admin: If your PC is part of a network in an organization, like a business, school, or government agency, your system administrator might have turned off the use of certain apps using the Group Policy. Contact your system admin if you believe that Group Policy is preventing you from using an app.

Method 7:

Make sure your apps are up-to-date: To make the apps working properly, you must keep your apps up-to-date. This could be done by turning on automatic updates in the Windows Store.

Method 8:

Contact the app publisher To view the publisher’s app support info, follow these steps:

1. On the Start screen, tap or click Store to open the Windows Store.
2. Search or browse for the app, and then tap or click it.
3. Scroll to the Details section of the app's description page, and then tap or click the support link for the app under Learn more. The link will open an email message for you to contact support or will take you to a support website.

If you do not possess the technical expertise required to accomplish this yourself or do not feel comfortable doing so, download and install a powerful automated tool to get the job done.

What is Runtime Error 339?

Runtime Error 339 is a common error code format that appears when a computer overloads with too much data. However, in some cases, it may occur due to the missing registry keys, DLL files, or during installation. It may lead some programs to shut down all of a sudden and may also corrupt files on the system.

Solution

Download Available to Completely Repair Runtime Error 339

Error Causes

This error code is alarming as it is a critical sign of an unstable system followed by improper maintenance of the computer. The potential risks associated with the Runtime Error 339 include:

• System startup issues
• Slow PC performance
• System crash and failure
• System file corruption

Therefore, to avoid these risks and system failure, it is advisable to fix the runtime error 339 immediately.

Further Information and Manual Repair

If you have a Runtime Error 339 issue on your computer, here is a great way how you can fix it right away:

Scan For Viruses

Improper maintenance of the computer indicates that your system might be exposed to viruses and malware. Viruses can modify the Windows registry and lead to Runtime Error 339. Therefore, first, it is important to scan for viruses on your PC.

Identify Software that Causes Errors

Scanning will help you identify software that produces this error on your PC. Once you identify them, either uninstall them or update the program. To uninstall the program, go to the Control Panel and then click on the Add/Remove program if you have Windows XP, if not then click on the Programs and Features item. Now delete the program from your system.

Obtain the Latest Version of the Installer and Re-install the Deleted Program

Once you get your hands on the latest version of the installer, run it on your system by following the on-screen instructions. Install the program. There is also another way to fix Runtime Error 339 and that is by downloading the Runtime Error tool.

Use a Professional Runtime Error Fixer Tool

To fix the error you can also use a professional Runtime Error fixer tool to scan for viruses on your PC. It is available for free download here. Download the tool and install it on your computer. Simply scan your PC after installation. Click the repair button once the scan is complete. This tool fixes problems in just a few minutes.

There is a lot of software on the market today, but from time to time we discover something extraordinary and unique worth sharing and today we have a threat for you. Ventoy is a tool that will help you with system reinstallations and system maintenance once and for all.

If you are a computer user that has multiple operating systems or you are installing and maintaining different hardware via different OS there is a high chance that you have multiple USB sticks with different operating systems on them.

Now the problem with that is that there are probably too many unlabeled sticks around or you do not have enough so you keep making system USBs depending on which one you might need.

Ventoy solves all of these problems by letting you have as many operating systems images as your USB has capacity. The only thing you need to do is get the software here: https://www.ventoy.net/en/index.html and make a USB with it, then you can freely just copy your ISO images onto the USB and once it is inserted into the computer you will be given a menu to choose which one you would like to start with, simple as that.

Features

• 100% open source (license)
• Very simple to use (Get started)
• Fast (limited only by the speed of copying the iso file)
• Can be installed in USB/Local Disk/SSD/NVMe/SD Card
• Directly boot from ISO/WIM/IMG/VHD(x)/EFI files, no extraction needed
• Support to browse and boot ISO/WIM/IMG/VHD(x)/EFI files in local disk Notes
• No need to be continuous in disk for ISO/WIM/IMG/VHD(x)/EFI files
• Both MBR and GPT partition styles are supported
• x86 Legacy BIOS, IA32 UEFI, x86_64 UEFI, ARM64 UEFI, MIPS64EL UEFI supported
• IA32/x86_64 UEFI Secure Boot supported Notes
• Linux Persistence supported Notes
• Windows auto installation supported Notes
• Linux auto installation supported Notes
• Variables Expansion supported for Windows/Linux auto-installation script Notes
• FAT32/exFAT/NTFS/UDF/XFS/Ext2(3)(4) supported for main partition
• ISO files larger than 4GB supported

• Menu alias, Menu tip message supported
• Password protect supported
• Native boot menu style for Legacy & UEFI
• Most types of OS supported, 1000+ iso files tested
• Linux vDisk(vhd/vdi/raw...) boot solution Notes
• Not only boot but also complete the installation process
• Menu dynamically switchable between ListView and TreeView mode Notes
• "Ventoy Compatible" concept
• Plugin Framework and GUI plugin configurator
• Injection of files into runtime environment
• Boot configuration file dynamically replacement
• Highly customizable theme and menu style
• USB drive write-protected support
• USB normal use unaffected
• Data nondestructive during a version upgrade
• No need to update Ventoy when a new distro is released

‘R6025 pure virtual function call’ is a runtime error that occurs suddenly on the screen and disrupts the program being run prior to it. This error display indicates that the program has been corrupted. R6025 runtime error usually occurs with the Visual C++ framework.

Solution

Error Causes

This error occurs when the C++ program crashes which is usually because of the malfunctioning or missing of the device driver or incomplete device driver files. It happens because your application indirectly calls a pure virtual member function in a context where a call to the function is invalid. Most of the time, the compiler detects it and reports it as an error when building the application. R6025 error is usually detected at run time.

Further Information and Manual Repair

To fix the R6025 pure virtual function call error, you need to find the call to the pure virtual function. After you find the call, you need to rewrite the code so that it is not called again. There are 2 ways to do this:

Alternative 1

One way to fix the R6025 pure virtual function call is to replace the function with an implementation that calls the Windows API function DebugBreak. The DebugBreak causes a hard-coded breakpoint. Once the code stops running at this breakpoint, it is easy for you to view the call stack. By viewing the call stack you can identify the place where the function was actually called.

Alternative 2

Another quick way to find a call to a pure virtual function to fix the R6025 error is to set a breakpoint on the _purecall function that is usually found in PureVirt.c. By breaking this function you can trace the problem occurring and rewrite the call to ensure the error does not occur and the program you are trying to develop on the Visual C++ framework is easily developed. If R6025 Error is related to Windows Registry Problem Then here’s how you can fix the problem: To fix the runtime error R6025, run registry cleaner software to scan and fix all errors.  This alternative is suitable if the R6025 error is related to the Windows registry problem and where the error has occurred due to corrupted or malicious registry entries. You can download the registry cleaner repair tool for free. Run it to scan errors and then click the fix error button to repair the problem immediately.