Increase or decrease notification display time

If your printer has been working just fine and you suddenly get an error message saying, Printer not activated, error code 30”, then something is definitely wrong and it’s not good especially if you have lots of things to do. Worry not, as this post will help you resolve the printer issue. Simply follow each one of the given options below carefully.

Option 1 – Try running the Printer Troubleshooter

The first thing you can to resolve the printer issue is running the Printer Troubleshooter. This built-in troubleshooter can detect and automatically fix the problem for you. To use it, follow these steps:

• Tap the Win + R keys to open the Run dialog box.
• Next, type “msdt.exe /id PrinterDiagnostic” in the field and click OK or hit Enter to open the Printer Troubleshooter.
• Then click the Next button and follow the next on-screen instructions to fix the issue with the printer.

Option 2 – Check if the concerned printer is set as the default one

It could be that the printer you are trying to use is not set as the default printer. This is mostly the case so to fix the issue, you need to set the concerned printer as default. To do that, follow the steps below.

• Tap the Win + I keys to open the Settings app.
• After opening Settings, select Devices from the menu and then click the Printers and scanners option.
• From there, look for the printer you are using among the list of options. After you find it, click on it and select the Manage option.
• Now click on the “Set as Default” option to set the printer as default.

Option 3 – Try updating the driver for USB Composite Device

The problem with your printer might also be caused by the USB Composite Device. It could be that the USB Composite Device is acting up. Thus, you need to remove and reinstall it. How? Follow the steps below.

• First, click the Start button and type “device manager”.
• Then click on the “Device Manager” from the search results to open it.
• From there, look for the USB Composite Device option and right-click on it, and select the Update Driver from the options.
• Restart your PC and then click the “Search automatically for updated driver software” option.
• Now uninstall and remove the printer driver software and reinstall it then refresh.

Option 4 – Try updating all the drivers for your Printer

• 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. Look for Print queues from the list of drivers displayed and click on it to see all the Printer drivers.
• Next, right-click on each one of the drivers and select “Update driver” to update the driver. Do it for all the Printer drivers
• After that, select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• Restart your PC and try printing a document again and see if the “Printer not activated, error code -30” no longer pops up.

Note: You also have the option to go directly to the website of your printer manufacturer and check if there’s a new update – if there is, download it.

Microsoft’s initial Windows 11 hardware requirements were not really well received by users and they were not really clearly represented from the start making a lot of potential customers slowly drift away from the hype. It seems that Microsoft has acknowledged this since they have changed their tune about system hardware requirements for the upcoming Windows 11. It seems that Windows 11 will be able to be officially installed on unsupported computers but with a little inconvenience.

What is a catch?

Windows 11 will still have the same hardware requirements and if the PC meets them, that computer will be officially supported, other ones (any that can run Windows 10) that do not meet system requirements can still run Windows 11 but the system will have to be clean installed. So no upgrade option for old computer users, just a clean install. This means of course that you will need to download the ISO image and make a bootable USB in order to install it. Also since you will be doing a clean install do a backup of the hard drive since it will need to be formatted. Also, Microsoft has stated that with unofficially supported PC some driver updates might not be delivered leaving you with either older driver versions or relying on your hardware manufacturer on them. This is still not confirmed by Microsoft, just stated as an option. We will see how it goes.

Conclusion

It is very good that Microsoft has reconsidered its system requirements and will not stubbornly push its initiatives over the top requirements allowing even older computers to install new OS. I am sure over time lot of users will upgrade their hardware and drive into officially supported waters, but it is good that they will be able to use new OS on their current hardware.

‘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.

This post will guide you in fixing the “Communication with service process failed” error in Windows 10. This error is related to the Intel Driver and Support Assistant application. Although this error does not reportedly cause any loss of functionality in the computer, however, it still indicates that there is something wrong with some of your driver modules. Intel has taken a bold step and combined its older modules into this new application (Intel Driver and Support Assistant) recently. This application enables users to scan their computers for any available updates from Intel. This is the main application of Intel and provides users a way to update their driver software automatically instead of manually updating it. However, with the recent reports submitted by some users, it seems that something is wrong with this application, and users to have to deal with the “Communication with service process failed” error. This error might be caused by several reasons, for one, it could be that the application is corrupted or incomplete in its nature which is possible since this is still a developing and newly released app. It could also be that there are other utilities or modules that conflict with the Intel software. Whichever the reason may be, you can try out the options given below to resolve the problem but before you proceed, make sure that you have an administrator account as well as an active and stable internet connection.

Option 1 – Disable DSATray in Startup

If you receive this error message every time you start your computer then this means that the application is not able to launch properly. Like pointed out, it could be that it is still incomplete in nature or it conflicts with other applications. Thus, you can try to disable the service from the startup and check if it fixes the problem.

• Tap the Win + R keys to open the Run dialog box.
• Then type “taskmgr” in the field and hit Enter to open the Task Manager.
• After that, go to the Startup tab and look for the Intel Driver and Support Assistant app.
• Right-click on the app and select Disable.
• Restart your PC and check if the error is now fixed or not

Option 2 – Reinstall the Intel Driver and Support Assistant

If the first option did not work, you can try reinstalling the Intel Driver and Support Assistant app. To do so, follow these steps:

• In the search box, type in “control” and then click on Control Panel (desktop app) among the search results.
• After that, select Programs and Features from the list which will give you a list of all the programs installed on your computer.
• From there, look for Intel Driver and Support Assistant and select it and then uninstall it.
• After you have the app uninstalled, open your browser and go to Intel’s official website. From there, download the driver utility manually.
• Once the download is finished, right-click on it and select “Run as administrator” and install the app on your PC with elevated access.
• Restart your PC and then check if the error is now fixed.

There is a central location in Windows 10 that allows users to view all the notifications from its Action Center. Aside from viewing notifications, users can also manage them and take necessary actions in just one single place. Notifications in Windows 10 look similar to a message icon but can be at variance in function. However, recently, a number of users reported that even though they receive notifications about new actions but when opening them, they see nothing. In other words, the notification is false, and to fix this, read on as this post will provide you a couple of workarounds. The Windows 10 Notifications and Action Center notification messages might show a mismatch. For instance, Windows 10 may say that you have some notifications but when you open Action Center, you find it empty and there are actually no notifications there. Take the case of the following screenshot, the Windows 10 Notification says that there are 6 new notifications available for viewing but the Action Center says otherwise. Before you troubleshoot the problem, you might want to run System Restore especially if you’ve made some changes in your computer prior to this issue which might have messed with the Windows 10 Notifications and Action Center. To perform System Restore, refer to these steps:

• First, press the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

If the problem wasn’t fixed and you’re still getting false notifications, you might want to troubleshoot the problem further using the options given below.

Option 1 – via Windows PowerShell

• In the Start search, type “PowerShell” in the field and hit Enter to pull up the Windows PowerShell window.
• Next, copy and paste this command and hit Enter to execute it: Get-AppxPackage | % { Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)AppxManifest.xml” -verbose }
• After that, reboot your computer and check if the false notifications are now gone.

Option 2 – Try renaming the Usrclass.dat file

DAT errors like the ones that are associated with the Usrclass.dat file, most likely occur during computer startup, program startup, or while you try to use a specific function in your program. Even so, it can easily be fixed. How? Refer to the given steps below.

• Tap the Win + R keys to open the Run dialog box.
• Then type %localappdata%MicrosoftWindows and hit Enter to get to the location of the UsrClass.dat file.
• After that, look for a file named UsrClass.dat and once you’ve found it, right-click on it and select the Rename option.
• Now rename the file to UsrClass.old.dat and then restart your computer and see if the problem is now fixed or not.

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.

Use third party automatic solution

If you are not tech-savvy or you do not wish to manually tackle with Windows system you can use RESTORO (guide and download link below) to automatically repair this error. RESTORO will automatically scan your system and fix all errors with just a single click of a mouse. If you wish to fix the error manually keep on reading.

.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

What is Error Code 100?

Error Code 100?? Whenever a Setup error contains error codes in the message, this indicates what the setup was operating on, let’s say copying files. The text in the error message will determine whether that it is fatal or not. An error code 100 is a system error that is displayed as ‘ERROR_TOO_MANY_SEMAPHORES’ or as a value 0x64. This error means that the system ‘cannot create another system semaphore.’ A semaphore is used in controlling access to parallel programming or a multi-user platform through multiple processes. This error can prevent certain features of your Windows to perform properly, like trying to get a print, copying files, deleting files, or any other routine computer activities.

Solution

Error Causes

Error code 100 can affect a wide range of activities that you normally perform on your PC. This error can occur for a number of reasons, of which some of the common ones include:

• When the Microsoft SQL Server fails to start the service
• When the account used for starting AOS does not match the database in SQL Server
• When the AOS licenses have exceeded their limit
• When the SQL Server database is incorrectly case sensitive

Though these are the common causes for error code 100, there can be other ways through which this error can occur. To find out the specific cause for error code 100, follow these steps:

• Go to Start and select All Programs. Go to Administrative Tools and click Even Viewer
• Click Application in Even Viewer
• Locate the error message in the right pane by scrolling down
• Click on the error message and see if the message applies to the error code.

Further Information and Manual Repair

In order to manually repair this error, you will have to work with your Network Administrator as they will have security privileges to take the steps. However, there are more than one ways to resolve this issue, for instance:

1. Starting SQL Server Service
   • A likely cause of an error code 100 can be that your SQL Server service is not started. To activate it, follow these steps:
   • Got to Start and Click on All Programs, go to Administrative Tools and click on Services
   • Find SQL/MSSQLServer service
   • Right Click on it and click Start to activate the service
2. Network Resolve

If you are connected to a network, then you can work with your network administrator to fix error code 100. Follow these steps to resolve this error:

• Got to Start and then Run. Type dcomcnfg and press Enter
• Locate Default Security and click it
• Find Default Access Permissions and click Edit Default
• You should locate System and Interactive, listed in the Allow Access. If they’re not listing, you can add them by clicking Add
• Find the local computer in the list and click on Allow Access
• Click Ok on the following three steps
• Log off the computer and log in again.

We couldn’t update system reserved partition” - What is it?

Customers will most likely encounter the “We couldn’t update system reserved partition” error when upgrading to Windows 10 from Windows 7 or Windows 8.1. This error may also come with error code 0xc1900104 or error code 0x800f0922.

Solution

Error Cause

“We couldn’t update system reserved partition” Windows 10 upgrade error is normally caused by too little space on the System Reserved Partition (SRP). The System Reserve Partition is an additional small partition created by Windows, which stores boot files. The SRP can be filled up with security apps and third-party anti-virus. Once this partition has insufficient space, the system will not be able to upgrade to Windows 10.

Further Information and Manual Repair

Caution: The following steps are complex and need to be done by experienced users especially using the command line. Once an error is made in entering commands, there’s a chance that your device can be put in a no-boot situation, or data stored on the device can possibly get lost.

To upgrade to Windows 10, your device needs to have at least 15MB free space on the System Reserved Partition. Follow the procedure below and then try upgrading again.

First, know if the System Reserved Partition is whether in GPT or MBR partition style:

1. Open the Run window by pressing the Windows key + R. Type msc in the window then press Enter.
2. Right-click on the Disk where SRP is located then select
3. Click over the Volumes
4. On the Partition Style line, you’ll see which partition style your device is using, either Master Boot Record (MBR) or GUID Partition Table (GPT)

Second, determine which method you will need:

Depending on what partition style your device has and whether you’re currently on Windows 7 or Windows 8/8.1, there are various methods you need to do.

Method 1: Windows 7 or 8/8.1 with GPT partition

1. Click on the Start button and search for cmd. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.
2. Type mountvol y: /s at the command prompt then press Enter. This command will add the Y: drive letter where you can access the System Partition.
3. Type taskkill /im explorer.exe /f then hit Enter. Afterward, restart explorer in Admin mode by typing exe and hitting Enter.

NOTE: While in Admin mode, some apps like OneNote will not run.

4. Open File Explorer then type Y:EFIMicrosoftBoot in the address bar. Hit Enter.
5. Choose the language folders you want to permanently delete. Language folders are named with four letters split with a hyphen. For instance, you want to delete the German language: choose de-DE.
6. Optional: You can also delete unused font files for more space. Type Y:EFIMicrosoftBootFonts in the address bar then press enter.
7. Once you permanently deleted the unnecessary files, reboot the device to return to explorer.exe to normal mode and remove the Y: drive letter.

Method 2: Windows 7 with MBR partition

Doing this method will make a permanent, but small increase in the free space of the device’s SRP.

1. Delete language folders

a. Open the Run window by pressing the Windows key + R. Type diskmgmt.msc then hit Enter. b. Select System Reserve partition then right-click on it.

c. Choose Change Drive Letter and Paths then select Add.

d. Type Y for the drive letter then click OK.

e. Click on the Start button and search for cmd. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.

f. Type Y: at the command prompt then press Enter.

g. Once you’ve switched to drive Y, type takeown /d y /r /f . then hit Enter.

NOTE: Ensure that the space and period after “f” is included in order for the command to work properly      

h. Type icacls Y:* /save %systemdrive%NTFSp.txt /c /t then hit Enter to back up the permission to the drive.

NOTE: Ensure that all files are marked as successful and that no files are marked as failed.

i. Type whoami then hit Enter. Record the username that appears. Afterwards, type icacls . /grant <username you got from whoami>:F /t then press Enter.

NOTE: Ensure that there’s no space between the username and “:F” or the command will not work.

j. In the File Explorer, open the SRP drive and select the Boot folder. Choose the             language folders you want to permanently delete. Language folders are named      with four letters split with a hyphen. For example: de-DE is the German language          while en-US is the U.S. English language.

2. Truncate the NTFS Log:

a. Open the Command Prompt then type chkdsk /L Y: to check the size of the NTFS Log. If the NTFS Log size is less than 5000KB, you need not truncate the file.

b. Type chkdsk /L:5000 /X /F then hit Enter to truncate the NTFS Log.

c. Return to Disk Management window. Select Action menu then select Check if the device’s SRP now has a larger amount of free space. Once there’s enough space, right click the System Reserve Partition then select Change Drive Letter and Paths. Choose Y: then select Remove.

3. If there’s still not enough available space after truncating the NTFS Log, resize the USN journal:

a. Open the command prompt then type fsutil usn queryjournal Y: to display the size in hex value. Convert the hex value to decimal then divide it by 1048576. The result you will get will be in MB. If the journal size is 30MB or more, proceed with truncating the file.

NOTE: To convert the Hex value to Decimal, open the Calculator app in Windows then choose View menu. Select Programmer then choose Hex. Type the Hex value then choose Dec.

b. Type fsutil usn deletejournal /D /N Y: then hit Enter to delete the journal. Type fsutil usn createjournal m=1500 a=1 Y: to recreate the journal having the new log size value.

4. Restore permissions

a. Type icacls Y: /restore %systemdrive%NTFSp.txt /c /t in the Command Prompt. Check if the files were successfully processed before proceeding. If you see a message saying some files failed while processing, this is normal since some of the files have already been deleted before performing a backup. However, if there are no successful files indicated, the command was not properly executed.

b. Type icacls . /grant system:f /t then hit Enter to adjust the ACL back to System. Now, you can set the owner of the drive by typing icacls Y: /setowner “SYSTEM” /t /c then press Enter.

c. Check if the device’s SRP now has enough free space by going back to Disk Management and refreshing the data. If the SRP already has sufficient space, you can now remove the drive letter. Right-click on the System Reserved Partition then choose Change Drive Letter and Paths. Select the Y: drive then choose Confirm deleting the drive letter by clicking OK.

Method 3: Windows 8/8.1 with MBR partition

This method makes a larger, but temporary, increase in the SRP free space.

1. Be sure you have an external drive having at least 250 MB free space and formatted as NFTS.

2. Open Run by pressing the Windows key + R. Type mscthen to choose the Recovery Partition. Right-click on it then choose Change Drive Letter and Paths.

3. Select Add then type Y for the drive letter, click

4. Click on the Start screen then type cmd in the search bar. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.

5. Switch to another drive by typing Y: in the command prompt. Once you’re in the drive Y, type takeown /d y /r /f .

NOTE: Ensure that space and period after “f” are included in order for the command to work properly.

6. Type whoami then hit Enter. Record the username that appears. Afterward, type icacls . /grant <username you got from whoami>:F /t then press Enter.

NOTE: Ensure that there’s no space between the username and “:F” or else the command will not work.

7. Once the command is completed, type attrib -s -r –h Y:RecoveryWindowsREwinre.wim then hit Enter.
8. Open File Explorer and check the drive letter of the external drive you’re using (In this case, let’s assume F: is the drive letter of the external drive so when you see F: for the rest of the steps, this means the drive letter of the external drive you’re using).
9. Type mkdir F:RecoveryWindowsRE in the Command Prompt then hit Enter. Afterward, type xcopy Y:RecoveryWindowsREwinre.wim F:RecoveryWindowsREwinre.wim /h
10. Type C:WindowsSystem32Reagentc /SetREImage /Path F:RecoveryWindowsRE /Target C:Windows to map the new path
11. Verify if the copy was successfully done then type del Y:RecoveryWindowsREwinre.wim /F
12. Return to Disk Management window. Click on the Action menu then hit Check if the device’s SRP now has a larger amount of available space. Once there’s enough space, you can proceed with the upgrade.
13. Upon completion of the upgrade, move back the wim file to the Recovery Partition. At this point, you can re-map now the location by:
    1. Open the Command Prompt then type xcopy F:RecoveryWindowsREwinre.wim Y:RecoveryWindowsREwinre.wim /h and press Enter.
    2. Type C:WindowsSystem32Reagentc /SetREImage /Path Y:RecoveryWindowsRE /Target C:Windows to re-map to the original path.
14. Return to the Disk Management window. Right-click on the Recovery Partition then choose Change Drive Letter and Paths. Select the Y: drive then choose Remove.

Method: Download a Powerful Automated Tool

Not inclined to go through a long and technical process (as highlighted above)? Download and install a powerful automated tool and get the job done in a jiffy.

Windows has tendencies to remember WIFI passwords so it can reconnect automatically to them. But from time to time we change passwords and Windows does not let us change it since he has network remembered. In this case, we will not be able to connect to the internet. In this helpful guide, we will let you know which steps you will need to take in order to solve this issue and to be able to connect to the internet again.

1. Restart Modem

   First thing first, restart your modem. Windows might see it as a new network and offer you to type in the password for it.

2. Update driver

   Sometimes the issue could be due to driver problems, open device manager and update WIFI driver or reinstall it.

3. Reset WIFI password

   Press ⊞ Windows + R type “Control” > hit Enter. Now click Network and Internet > Network and Sharing Center > Change adapter settings. Right-click on the connected Wifi and select Status. Click Wireless Properties, change the password from the Network security key section, and then click OK to reset your WiFi password.

4. Forget the network

   Click on Start > Settings > Network & Internet > Wi-Fi. Click the Manage known networks link Select the network you are looking for Select Forget.

5. Delete your WIFI profile

   Press ⊞ Windows + X to open the secret menu and click on Command prompt (admin) In command prompt windows type: netsh wlan show profile netsh wlan delete profile name=<profile name> Reboot

The first major update for Windows 11, 22000.65 has brought some bug fixes and some new features. The previous update was just a bunch of small fixes but this time Microsoft has brought much more with this one.

Bug and security fixes:

• Patch for the PrintNightmare vulnerability.
• Taskbar icons not displaying after you rotate the screen back and forth.
• Date and time not following format settings.
• Contrast issues with File Explorer title bar
• Search dropping the first keystroke when you press the Windows key and type
• Blurry windows in ALT + Tab

Besides bug and security fixed newest update has also brought us some functional changes:

• The start menu can no longer be moved from center
• A search box appears at the top of the Start menu.
• Taskbar appears on secondary monitors.
• The refresh option appears on the jump list when you right-click the desktop. It was on the "Show more options" list before.
• New look for certain dialog boxes such as "battery low" or "display change"
• New snap layouts for portrait mode screens.
• Option to troubleshoot sound problems when you right-click the volume icon.
• Power mode settings on Power & battery settings menu.
• Right-clicking .ps1 files offers a "Run with PowerShell" option.
• New GIFs in the emoji panel in China

Honestly, I really like a search box on top of the start menu but really dislike the option to move it to left, I am sure that there are a lot of users who would feel more like at home if they could still move and set Windows to function and work how they want. It is very strange to me that Windows 10 was made to be so user-focused and been able to be user specific and Windows 1 takes most of these things away. I am not sure why Microsoft is going this way but I cannot really see how moving the taskbar on left is a programming issue or why it is wrong for example.