What to do if Cortana Search Box turned white

We are all waiting for the release of Intel’s Alder Lake series of processors and real-world results on its performance. Sadly lately it came to our attention that some games might have issues with the processor. Now before you go on the bandwagon on bashing Intel itself take note that it is not Intel’s fault at all. The issue that arises is mostly due to DRM software and how it works. As you might know or not, Alder Lake has two sets of cores, standard performance cores, and power cores, and with Intel’s Thread Director on-chip right cores will be used for the right tasks, and here lies the issue. DRM software might detect Thread Director as something suspicious and malicious, and then cut access to the game because of this. Intel, of course, has reached DRM manufacturers and places documentation about how software should be developed with this hybrid technology in mind. Of course, newer games will be updated if needed and everything will work fine, also games on GOG will work fine because of GOG’s policy of no DRM store but some older ones might be left in limbo. They could work fine but DRM might be triggered and prevent them from loading, usually, game developer itself removes DRM protection after some time but that is not really always the case and there is a chance that some games might simply just not work on Alder Lake CPU only because of DRM protection.

Conclusion

I will admit that I have not been a great fan of DRM in general, I understand that game developer want to protect themselves from piracy but how it looks they were not really successful with it. Even today single-player games get pirated on the day they are released and legally bought ones always make trouble for people that actually paid for them. I remember times when DRM was awful and you could install a game a limited number of times, luckily this was removed but it seems that many old habits still remain sadly and DRM is present even today in various forms. GOG is proof that people will buy DRM-free games and that they will support this kind of model. Maybe it is time to forget about fighting against piracy, you will not make it go away and people who do not want to buy games will not buy them, on other hand many users that do buy games, if they cannot use them they will rest to pirated version since that one will work. It is sad to see that pirated software can work better than a legal one and offer a more pleasant experience.

Modem Error 633 error is a dial-up error that usually occurs when using a USB modem with a Windows computer. The Modem Error 633 error message is displayed as the following:

“Error 633: The Modem is already in use or not configured properly.”

Solution

Error Causes

This error can be triggered due to several reasons such as:

• A software program conflicts with the USB modem
• The modem is not configured properly
• The Telephon.ini file is missing or damaged
• There is some issue with the way Windows is managing the communication (COM) ports on your computer.

Further Information and Manual Repair

If you experience the Modem Error 633 on your PC, you don’t have to panic. Though this error does not pose any major threats like data loss, it may hamper your ability to use the internet therefore it is advisable to resolve the error. Repairing the Modem Error 633 is quite easy. There are a number of ways to fix this error. So, let’s get started:

Solution 1: Delete Incompatible Software and Non-Present Modems

• Click on the start menu and go to the ‘Control Panel’. Now choose the option ‘Phone and Modem’.
• Here you will see three tabs, the dialing rules, modems, and advanced. Choose the tab ‘Modems’. As you click on it, you will see modems installed on your PC. To repair the Modem Error 633, select and remove all the incompatible software and modems that are not present and click ‘OK’.
• Now to bring the changes into effect, restart your system with the modem plugged in and try connecting to the internet again.

Solution 2: Change the Communication Ports

If the error occurs because the modem is not properly configured, then this solution is possibly the best way to resolve this error. Here’s what you need to do:

• Click on the Start menu and choose My Computer.
• Now click on the option ‘Manage’ to open the Computer Management Window.
• Once it opens, click the option ‘Device Manager and then expand the option modems. Click on Properties, then the Advanced tab, and the Advanced Port Settings button.
• As you click on the Advanced Port Settings, then click on the COM Port Number drop-down box.
• Choose a new Communication Port. However, make sure it is not already in use.
• Once you make changes, click ‘OK’ and then restart your PC.
• Now Open Device Manager again. Open the Modern Properties Window and then Click the Diagnostics tab.
• After that view the command response window to verify if the error is fixed. If yes, then create a new dial-up connection and connect to the internet with ease.

Solution 3: Disable the Startup items

• Another way to resolve Modem Error 633 on your PC is to go to the start menu and type ‘msconfig’ into the search box and then press ‘enter’.
• Open the misconfig.exe program. As you open it, you will see 4 tabs, General, Boot, Service, Start-up, and Tools.
• Now click on the ‘Start-up’, ‘Disable All’, and then press Apply.
• After you press Apply, a window will pop up asking to restart the computer.
• Confirm it and click restart.
• Once the computer restarts now try connecting to the internet again. This will hopefully resolve the Modem Error 633.

It has been some time since the release of Diablo 2 resurrected and overall reception was pretty good. People are enjoying the old classic game in hi-def. resolution and with new and improved visuals. Sadly some server issues are present still until this day and somewhat spoil the experience for players. The greatest lag and server crashes are pinpointed to game-creating events. When a player creates a new online game, the server needs to pull a lot of details from the database and make a game, due to some legacy code present this process takes some time and it is demanding a bit on the server-side, and although code was optimized to cater to more modern approach some legacy code still remains. Another thing that was spotted to affect performance itself is player behavior, to be more specific, modern gamer behavior. Where players find good builds and runs on the internet and then go to farm-specific areas or bosses for loot or experience points, which in return boils down to making plenty and short runs that are made by creating games and after run eliminating them. Now pair that with the previous statement about legacy server and database code and you can add 1 and 1 and see how this might be an issue. A lot of short games over legacy code are placing games in a state it was not designed for back in 2001 and therefore we have issues. Sadly solutions without completely rewriting the whole code are not very promising and they include rate limiting, which will prevent players to create many games in succession in a short period of time and maybe even login queues to drop a load on servers. Blizzard reached to people in the whole company, even old diablo 2 developers to ask for advice and they say that they are working on solutions so they could lift limitations and have everything running fine.

Microsoft just released Windows 11 ISo file, based on the latest Insider Preview Build 22000.132. Inside build, you can try all-new features like clock updated app, snip tool, and everything releases so far via various patches. You can also use Windows 11 ISO file to do a clean install on your computer, but if you go with this option all of your existing files will be deleted. Microsoft says it added the ability to name your PC during the setup experience. You’ll also get to experience the Get Started app that’s designed to help you get going on your new Windows 11 PC (even if it’s not actually a new one).

Download ISO

• Go to the Windows Insider Downloads page. You will need to sign in with a Microsoft account registered with the Insider Program.
• Scroll down to Select Edition and select the build you want to download. You will most likely want the one at the top from the developer channel, as this is where Windows 11 should arrive first. So far, only Windows 10 builds are available. Click confirm.
• Select your preferred language. Not all languages ​​available for Windows are compatible with the Insider program, so you may have to stop depending on where you are from.
• Click the download button and the ISO file will start downloading.
• This is definitely an easier method, but unfortunately, it is not available yet. We will update this article once Windows Insider ISOs are available. Later, once Windows 11 64 bit is available to everyone, you can also download the stable build of Windows 11 iso. Microsoft offers the Media Creation Tool and Upgrade Assistant, which usually do just that. It will be some time before Windows 11 versions of the tools are available, as the operating system is only getting closer to this holiday.

If you encounter a blank page with an error message saying, “Origin Error” when you try to load a webpage, then this post will surely help you resolve this error. As you can see, this error is a very uncommon one and it is not about the popular game known as Origin where all you have to do is reinstall the client. Although this error message is a very uncommon one, you will see a blank page with a message saying, “Origin Error” when you attempt to load a webpage. To fix this error, this post will provide you some potential fixes that might help. Follow the fixes given below carefully and see which one fixes the problem.

Option 1 – Use Ctrl + F5 keys to clear browser cache

The first thing you can try is to “Hard Refresh” to clear the cache of your browsers. You can do that by using the Ctrl + F5 keys on your keyboard. On the other hand, you can also clear the cache manually for Chrome, Edge, and Firefox.

Option 2 – Remove the Proxy

You might also want to try removing the Proxy as it could also help you in fixing the Origin error. Here’s how you can do it:

• Tap the Win + R keys to open the Run dialog box.
• Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
• After that, go to the Connections tab and select the LAN settings.
• From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
• Now click the OK and the Apply buttons.
• Restart your PC.

Note: If you are using a third-party proxy service, you have to disable it.

Option 3 – Try to flush the DNS, reset Winsock and the TCP/IP

You might also want to flush the DNS and reset Winsock as well as reset TCP/IP as it could help in fixing the Origin error. To do so, refer to these steps:

• Click the Start button and type in “command prompt” in the field.
• From the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
• After opening Command Prompt, you have to type each one of the commands listed below. Just make sure that after you type each command, you hit Enter
  • ipconfig /release
  • ipconfig /all
  • ipconfig /flushdns
  • ipconfig /renew
  • netsh int ip set dns
  • netsh winsock reset

After you key in the commands listed above, the DNS cache will be flushed and the Winsock, as well as the TCP/IP, will reset.

• Now restart your computer and open Google Chrome then try opening the website you were trying to open earlier.

Option 4 – Try using Google Public DNS

You might want to try changing your current DNS to the Google Public DNS. All you have to do is change the DNS settings explicitly on your operating system by using the DNS IP addresses. Here’s are the steps to do that:

• The first thing you have to do is right-click on the network icon in the Taskbar and select Network and Sharing Center.
• Next, click on the “Change Adapter Settings” option.
• After that, search for the network connection that you are using to connect to the internet. Note that the option might be “Wireless Connection” or “Local Area Connection”.
• Right-click on your network connection and click on Properties.
• Then select the new window to choose the “Internet Protocol 4 (TCP/IPv4)” option.
• After that, click on the Properties button and click the checkbox in the new window for the option “Use the following DNS server addresses”.
• Type in “8.8.8” and “8.8.4.4” and click OK and exit.

If you suddenly encounter PFN_LIST_CORRUPT Blue Screen of Death error while using your computer then it means that the Page Frame Number or PFN list is corrupted. Page Frame Number is an indexing number used by the hard drive to find out the location of every single file on the physical disk. This kind of Blue Screen error is usually caused by a driver that’s passing a bad memory descriptor list and it can either be temporary or permanent. And so to fix this particular BSOD error, read on as this post contains a couple of suggestions that could help. Keep in mind that when you get a Blue Screen error like PFN_LIST_CORRUPT, the power connection to your PC must not be interrupted and so if you are using a laptop, it’s best if you connect it to a power source. On the other hand, if creating a dump from 0% to 100% takes up more than 5-10 minutes, then you have to force shut down your computer by pressing and holding the Power Key for 10 seconds or at least until the CPU lights turn off. After you do that, proceed to the troubleshooting tips prepared below.

Option 1 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like PFN_LIST_CORRUPT. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Option 2 – Run a System File Checker scan

You can also try to run a System File Checker or SFC scan in order to scan your computer for corrupted files that might be the cause behind the PFN_LIST_CORRUPT error. Once it finds any corrupted system files, it will automatically fix them. To run System File Checker, here’s what you have to do:

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Restart your computer after the scan is completed.

Option 3 – Check for any hard disk errors

• On your desktop, right-click on the “This PC” or computer icon and then select Manage to open the Disk Management. Here you get to check your drive’s health.
• Next, click on Disk Management on the left side panel.
• From there, check the state of your drives. If it shows that all your partitions are healthy then it means all is good and that the problem may have something to do with some physical issues with your hard drive.

You might also want to run the CHKDSK utility to help you fix any issues with your hard disk. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f /r

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

Option 4 – Update the Device drivers

Updating the Device drivers can also help you fix the PFN_LIST_CORRUPT Blue Screen error. To do so, follow the steps below.

• Tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. If you see a red or yellow sign that shows up against the driver, right-click on the driver and select “Update Driver Software”.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• Restart your PC and then check if the Blue Screen error is now fixed or not.

Option 5 – Disable OneDrive

The PFN_LIST_CORRUPT error might also be caused by OneDrive. Thus, you have to try disabling this program to resolve the problem.

• Tap the Ctrl + Shift + Esc keys to open the Task Manager.
• Once the Task Manager is open, click on More Details located at the bottom left portion of the window.
• Then go to the Startup tab and select Microsoft OneDrive and then click Disable.

Usually when online service is not working or when something goes wrong online it is DNS, well that is what most of the time is the case. And yes, DNS or Domain Name Server seems to be an issue with Facebook being completely down along with Instagram and wassap. The true cause is that there is no working Border Gateway Protocol (BGP) routes into Facebook's sites. BGP is the standardized exterior gateway protocol used to exchange routing and reachability information between the internet top-level autonomous systems (AS). Most people, indeed most network administrators, never need to deal with BGP. Cloudflare VP Dane Knecht was the first to report the underlying BGP problem. This meant, as Kevin Beaumont, former Microsoft's Head of Security Operations Centre, tweeted, "By not having BGP announcements for your DNS name servers, DNS falls apart = nobody can find you on the internet. Same with WhatsApp btw. Facebook has basically de-platformed themselves from their own platform." Many people are very annoyed by this and with the fact that they cannot use their social media platforms but it seems that Facebook employees are in even bigger annoyance as it was reported that Facebook employees can't enter their buildings because their "smart" badges and doors were also disabled by this network failure. If true, Facebook's people literally can't enter the building to fix things. Reddit user u/ramenporn, who claimed to be a Facebook employee working on bringing the social network back from the dead, reported, before he deleted his account and his messages: "DNS for FB services has been affected and this is likely a symptom of the actual issue, and that's that BGP peering with Facebook peering routers has gone down, very likely due to a configuration change that went into effect shortly before the outages happened (started roughly 1540 UTC). There are people now trying to gain access to the peering routers to implement fixes, but the people with physical access is separate from the people with knowledge of how to actually authenticate to the systems and people who know what to actually do, so there is now a logistical challenge with getting all that knowledge unified. Part of this is also due to lower staffing in data centers due to pandemic measures." Ramenporn also stated that it wasn't an attack, but a mistaken configuration change made via a web interface. Both BGP and DNS are down, the "connection to the outside world is down, remote access to those tools don't exist anymore, so the emergency procedure is to gain physical access to the peering routers and do all the configuration locally." Technicians on site don't know how to do that and senior network administrators aren't on site. It seems that it will all be down for a couple of more hours before the issue is resolved.

Windows has a built-in Backup and Restore system so if the Windows Backup or Restore fails and you receive any of the errors 0x80070001, 0x81000037, 0x80070003, worry not for this post will guide you in fixing the problem. You might not be able to browse to the folders and files that you want to restore in the File Restore Wizard. The cause of the error could vary depending on what error code you receive:

• 0x80070001 – If you got this particular error code when trying to back up a specific library or when you accept the default settings in Windows Backup and Restore.
• 0x81000037 – If you got this kind of error code when you try to read from the shadow copy on one of the volumes being backed up.
• 0x80070003 – If you got this error code when trying to restore the folders or files in a library by using the Windows Backup and Restore.
• On the other hand, you cannot use the Browse for files or the Browse for folders functionality.

Note that the Windows Backup or Restore failed, Errors 0x80070001, 0x81000037, 0x80070003 Error code 0x80070001, 0x81000037 occurs during backup while Error code 0x80070003 and “Browse for Files” issue occurs when you try to restore files. Whichever error codes you got, here are some possible fixes that might help.

Option 1 – Fix Windows Backup error codes 0x80070001, 0x81000037

The reason for the Windows Backup error codes 0x80070001, 0x81000037, as mentioned above, is when there is a volume that uses a FAT file system (0x80070001) and when a volume contains compressed files (0x81000037). To fix these errors, you need to remove the “reparse point” also known as SYMBOLIC LINK, and select the absolute path of this location in the Windows Backup configuration user interface. Refer to these steps to remove the reparse point.

• Tap the Win + R keys to open the Run dialog box.
• Then type “cmd” in the field and hit Enter to open Command Prompt.
• Next, type the following command and hit Enter:

DIR /AL /S

• After you enter the command, it will display the JUNCTION list.
• Now to delete the mounted volume reparse point, you have to locate the reparse point you found and right-click on the reparse point icon, and click on Properties.
• Confirm that the folder Type is Mounted Volume in the General tab and then delete this folder.

Option 2 – Fix the Windows Restore Error 0x81000037

When you try to restore a deleted backed-up directory, it fails and the Error code 0x81000037 pops up. You can also encounter this error when you select to restore the files to their original subfolders check box in the File Restore Wizard and you try to restore folders or files to an alternative location, then you will encounter error code 0x81000037 which will be displayed in an error message as shown below: To fix this error, you need to re-create the missing directory using the following steps:

• Take note of the path for which the error occurs.
• Then create the corresponding folder.
• Now perform the restore operation again.

And since you might have subfolders in the deleted folder, click to clear the “Restore the files to their original subfolders” checkbox when you run the File Restore Wizard.

Option 3 – Cannot use the Browse for files or the Browse for folders functionality

There is no proper fix for this particular error but if you remember the name of the files, you can just search for them. Click on the Search button when using the File Restore functionality and then type the name of the file and when that file appears, select and click on it to restore it.

If you like to schedule different tasks on your Windows 10 computer and automate them, then you would find the Windows Task Scheduler very useful. It is commonly used by a lot of users to schedule various tasks like scheduling periodic execution of scripts and some programs to make sure that the intended tasks are automatically carried out. Apart from being a preinstalled application, the Task Scheduler is already available on your computer. However, there are times when you might encounter some errors while using it. One of these errors is error 0xFFFD0000. You can encounter this error while executing some PowerShell scripts. It can occur to any tasks as well especially to the ones that have a file executed using a particular program. And just like the PowerShell script, files also use PowerShell to be executed. To fix Error 0xFFFD0000, you need to follow the instructions provided below carefully. Step 1: In the Start Search, type “task scheduler” and click on Task Scheduler from the results to open it. Step 2: After opening Task Scheduler, right-click on the task that’s giving you the error and then click on Properties. Step 3: After that, navigate to the Actions tab in the new mini window that appears. Step 4: From there, select the action for the task and click on the Edit button which will open another mini window. Step 5: Next, make sure that the path to the executing program is properly typed inside the field of Program/script. Note that it should be set to the executable file for that particular program. For instance, you have to set it to “C:WindowsSystem32WindowsPowerShellv1.0powershell.exe” for the Windows PowerShell program. Step 6: You can also utilize the Browse button and navigate through Windows Explorer to locate that particular executable file for the program. Step 7: Now make sure to use the file argument in the Add arguments field followed by the path of the file to be executed. It should look like this:

-file "C:/Users/Ayush/Desktop/Powershell Script Sample.ps1"

Step 8: Once done, click on OK to save the changes made and see if the task is still giving you an error or not. On the other hand, if you are still getting the same error, you can try to repair the Task Scheduler by deleting corrupted tasks. Note that a single corrupted file can cause big problems so this option is quite important. And for you to delete a corrupted task or any task from the Task Scheduler, you have to use the Registry Editor if you are not able to use the Task Scheduler interface. To do so, follow these steps:

• Tap the Win + R keys to open the dialog box for Run.
• Next, type in regedit and click on OK or tap Enter to open the Registry Editor.
• Then navigate to this path: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTree

Note: In this path, you can see all the tasks that are currently set in the Task Scheduler. And since it would be hard to tell which one of them is corrupted, you have to delete the latest one in Task Scheduler last. But before you do so, make sure that you take a note of the ID of the tasks. And for you to get the ID, you have to select the task you wish to delete and double click on the ID string located on your right-hand side, and then copy it in the Notepad.

• Right-click on the task name and then delete it.
• After that, delete the very same GUID which you have copied earlier from these folders:
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheBoot
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheLogon
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheMaintenance
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCachePlain
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTasks

Note: You might not see the same GUID from these folders but if you see it, delete it right away.

• Next, navigate to this location: C:WindowsSystem32Tasks
• Delete the very same tasks you just deleted from the Registry Editor.
• Restart your PC and check if the Task Scheduler is back to its normal state or not.

File Transfer Protocol Server, also known as FTP Server, is a private or public service that can host files that can be accessed both locally and globally. It is a quick, flexible and seamless service that allows you to store any kind of files depending on the total size of the server. If you’ve always found an FTP server useful, then the good thing is you can now create your FTP server since Windows 10 now allows it. You can host this server locally and later on make it globally available via the internet. So if you are planning to set up an FTP server on your Windows 10 computer, read on as this post will guide you on how to do so.

To set up the FTP server, you need to configure it first and then configure the Windows Firewall for the connections to go through. For more details, refer to the following steps:

Step 1: You need to configure the FTP server on Windows 10.

• In the Search box, type in “Turn Windows Features On or Off” to search for it.
• Then click on the appropriate result which will open a mini window.
• From this mini window, scroll down to the list and expand “Internet Information Services where you have to expand the FTP Server section.
• Next, select all the checkboxes to enable all the entries under FTP Server and then click the OK button to apply the changes made.
• And now, since your computer is now allowed to host an FTP server, you need to configure it. To do so, type “Internet Information Services (IIS) Manager” in the Search box and click on the appropriate entry.
• Next, right-click on Sites under the navigation bar of Connections and select Add FTP Site. This will open a new window where you have to input some information about your FTP hosting.
• Now enter the details and click on Next.
• Upon clicking Next, you will be prompted to give some authentication details. Enter the following details in the screenshot below.
• Now click on Finish. After that, you will get an FTP Server being hosted on your Windows 10 PC.

And now that you’ve successfully configured the FTP Server, the next thing you have to do is to allow connections from and to the FTP server. Refer to the next step below. Step 2: Configure the Windows Firewall for FTP connections to pass-through

• In the Start Search, type “Allow an app or feature through Windows Firewall” and click on the related search result which will open a window with all the settings.
• From there, click on the Change Settings button. This will display a list where you have to mark all the checkboxes for the FTP server to enable them in both the Private and Public configurations.
• After that, click OK. This will allow you access to the FTP server on your local network.