If you have multiple products with Windows on them, Copy & Paste text between them is easy as 1,2,3 and we will be happy to tell you how can you do it.
Hello and welcome everyone, today we will see how can we share text information between 2 devices using Windows 10 in instant. In order for you to be able to share text information between devices, there are two prerequisites that you must meet. The first is that all devices must be connected to the internet, the second is that you must have a Microsoft account.
If you have both of these things continue with the tutorial, if you do not have a Microsoft account go to Microsoft website and create one for free.
Also, know that this option needs to be turned ON on all devices in order to work. So steps we will explain will have to be done on each device, if you already have some device logged in and connected to Microsoft account, you can skip setting it up.
Click on ⊞ WINDOWS and click on settings.
Then click on System.
Once you are in the system, on the left tabs find and click on Clipboard.
If you are not logged in to your Microsoft account do so on the right panel by locating Sync across devices and click on sign in.
When you are signed in click on the option to turn it on.
One option is turned ON, you will be greeted with two choices, to copy everything from the clipboard automatically or to choose text which you want to sync and paste it with ⊞ WINDOWS + V. Choose whatever better suits your needs, and you are done.
Repeat these steps for other devices and you are done.

When you upgrade your Windows 7 or Windows 8.1 system to Windows 10, you’ll undergo a phase called Out of Box Experience, or simply OOBE. This phase is intended to allow users to customize their Windows 10 experience, which includes defining personal settings, creating user accounts, and more. Some users reported having issues when creating their user account during the Out of Box Experience (OOBE) on Windows 10 upgrade. Some also reported issues about non-responsive behavior (Welcome Back) page.
Error CausesUnfortunately, there’s no known cause for this error. However, some users reported that this occurs when:
Your Windows 10 upgrade will not be successful if you’re not able to create a user account or finish the Out of the Box (OOBE) phase of the installation. Here are some methods that will help you fix this manually.
Some users reported that waiting for about an hour and retrying the process again will solve this problem. It’s also recommended that you keep your computer in a ventilated place while you wait to retry the process.
This method has 2 requirements in order to work.
If you meet these two requirements, you can solve the error by following the steps below:
This method only applies if you’re a laptop user.
Instead of connecting to a Microsoft Account after the set-up, you might want to try creating a local account. To do this, follow the steps below:
If the steps above don’t work, you might want to try Startup repair.
In order to do this step, you need to have official Windows 10 ISO files.
After doing the steps above, there’s a chance you get an error message that says “installation cannot be completed in safe mode”. When you see this, just press Shift+F10. This will execute and open the command prompt of your computer.
From the command prompt, you can try and create a new user account.
For example, net user Username Password /add
The username here should be replaced with the account name you want to add, and the Password here should be replaced with the password you want to use for the account.
After replacing the username and password on the text, press the Enter button on your keyboard. You’ll know if the command is successful once you see the message, “The command completed successfully.”
You can now close the command prompt. Restart your computer and try to log in using the account you just created.
If all the above methods still don’t work, it might be best to try automated software to help you fix this problem.
Most of the time running applications with typical settings is fine but from time to time we might have some applications that will require running with administrator privilege in order to work properly. In this case, it is very easy to do it, you just right-click and choose run as administrator.
Although a very easy solution, it can be quite annoying if running the app is on a daily basis or even more times per day. If this is the case then right-clicking and choosing to run as administrator can be a daunting task, sometimes you can even forget to run it like this in heat of work and some unforeseen consequences might occur.
Luckily there is an easy hack so you can open the chosen application each time as an administrator with a simple double click each time.
Error code 0x8007267C is specific to Windows 10. This error is triggered when no DNS server is currently configured in your network settings during the Activation process. If you are fairly confident in your ability to address command-line tools and networking issues, you can follow the steps below to try to remedy the error code on your own. If not, you may need to contact a qualified technician in order to resolve the error successfully.
Error CausesThe cause of Error Code 0X8007267C within the Window 10 system is fairly straightforward. Windows Activation requires a valid DNS server to be configured in order to complete the Activation process; if one is not available or properly configured, then you may see this error code and Activation will fail.
The following methods may help you to resolve this error, but you’ll need to have some familiarity with command-line tools to complete the steps successfully. If these methods do not work or if you are uncomfortable in using the command prompt, you may need to consult a technician to fully resolve this particular error code on the Windows 10 system.
In order to resolve this error code, client connectivity to a DNS server must first be established. The following steps may help you to determine the root problem with your connectivity status:
ping <DNS Server IP address>
If basic connectivity to the DNS server in question is failing, then you will need to resolve that issue before going further in the process.
After troubleshooting the above basic connectivity issues to the DNS server, you can reattempt Windows Activation by using the command below from within an Elevated Command selection:
cscript windowssystem32slmgr.vbs -ato
If the steps above did not work for you, you may want to try the steps found in method 2.
If a DNS server is not connected to your network, you can use an alternative method to complete the Windows Activation process. Bypass Method 1 by using a MAK product key instead to activate the volume license installation. Certain MAK product key providers have a variation on the specific key numbers that you will need to use. If you are using TechNet media or MSDN media, you will have to change the product key listed to the product key provided. The product keys provided by either TechNet media or MSDN media for Windows Server 2008 or for Windows Vista Enterprise will be the MAK product key that you will enter in a later step.
Like the previous method, you will need to have some familiarity or confidence in your ability to operate Command Line tools before proceeding. Once you have found your MAK product key, you’ll need to open a command prompt and use the following command to change the product key to match the MAK product key, which should look something like the example below:
slmgr –ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
After completing the product key change, use the following command to initiate the phone activation wizard, thereby completing the activation of the system:
slui 04
The activation wizard should be able to walk you through the remainder of the process in a step-by-step manner. In addition to appearing as an error code in Windows 10, this particular error may apply to multiple versions of Windows, including:
Steps to address the error code may be different in any of these other versions of Windows. If you have difficulty in resolving the error effectively, seek professional technical help.
“Windows could not configure one or more system components. To install Windows restart the computer with error code 0xc1900101-0x30018.”When you check on the Windows 10 rollback log, you will see a part with the “iisetup.exe” that’s related to the abort. Usually, the upgrade process completes over 50% and gets stuck and then rolls back later on and generates the error logs. This kind of error, in most cases, appears during the upgrade of Windows 10 and is related to the Internet Information Services or IIS in Windows 10. For some unknown reason, it restricts the installation or the upgrade which causes the error to appear. To fix the “Windows could not configure one or more system components” error, you can try to remove the IIS from the Windows Features or rename the “inetsrv” folder. You could also move all the folders related to IIS to another drive. For more details, refer to the options provided below.
Valve has officially announced that Steam Deck will be compatible with Windows 11 despite TPM 2.0 Microsoft requirements.
From the beginning, Deck was announced like a mini handheld PC device. Powered with new Steam OS 3.0 based on Linux. However, besides out-of-the-box OS it was also stated that Deck will be a personal device meaning that other PC-based operating systems could be installed on it and even run your typical applications in it.
Since Microsoft announced Windows 11 hardware requirements, specifically the TPM 2.0 requirement many users voiced concern that Steam Deck will not be able to connect to Windows 11
TPM 2.0 is something that Microsoft requires for every internal and hardware component that is to connect on a Windows 11 device. This is to ensure that only trusted devices would be included in the array of a PC setup and avoid any problems like malicious hardware injecting software into a system.
This would also minimize the compromise Windows would have, as unverified or untrusted devices connect to a Windows PC.
However, Valve and AMD are ensuring us that Deck will not have any issue connecting to a PC running Windows 11 or even if you wish to transform Deck itself into a Device running Windows 11.