So let's dive into this cool handheld in more detail and find out why we like it so much.
There are a lot of online services and a lot of ways to get your public IP address. One of them being typing whats my IP in Google search and you will get immediate results. But there is a way to get the same information inside Windows 10 which could be very useful if for any reason you can not connect to mentioned services. By checking public IP directly inside your windows you can make sure that the issue for not being able to open some websites is not due to your public IP.
In order to use this Windows feature, we will be checking our public IP using Windows PowerShell.
To open Power Shell in Windows first press ⊞ WINDOWS + R to open the run dialog
Inside run dialog type Powershell and press ENTER
In the Powershell type in the following command and press ENTER
(Invoke-WebRequest -uri "http://ifconfig.me/ip").Content
When the command finishes you will see what is your public IP address, if you wish to know more about your connection type in and press ENTER:
Invoke-RestMethod -Uri ('https://ipinfo.io/')
This command will provide you with further information like city, region, country, and others.

So let's dive into this cool handheld in more detail and find out why we like it so much.
After upgrading to Windows 10 operating system from Windows 7 or Windows 8/8.1, a lot of Windows users are complaining about the Windows setup in a continuous reboot loop. The computer would just keep on rebooting every time the machine is booted and this incites frustration for a lot of Windows users.
Error CausesWhen Windows launched the third update for Windows 10, users trying to upgrade to Windows 10 encountered an endless reboot loop problem. The computer will crash repeatedly. The KB3081424, which is a roll-up of bug fixes of Windows 10, continuously fails once you start the update process and then triggers a message showing: “We couldn’t complete the updates, undoing the changes.” The undoing process will then cause a system reboot mandatorily.
Once you log back on your computer again, the Windows 10 update will try to reinstall KB3081424. You will not be able to stop the update which will cause your Windows setup in a continuous reboot loop.
The KB3081424 will not be successfully installed since if it fails for the first time, that initial failure can be detected to create a bad entry in your Windows 10 registry. This will then prevent your subsequent attempts to reinstall KB3081424 to make it work correctly.
In order to fix the problem of Windows 10 setup in a continuous reboot loop, there are a few methods you can try. Try following these simple steps and you’ll be able to get rid of the problem.
Note: If you’re not highly confident to solve this issue on your own, it is highly recommended to consult an authorized computer technician who would be knowledgeable enough to fix the issue for you. In addition, you can also use a system optimizer to resolve the issue.
Microsoft Windows released an updated fix for the Windows setup in continuous reboot loop problem. You can try fixing the issue through Windows Update.
Before KB3081424 attempts to install again, you can try doing this solution:
Another thing you can try to solve the Windows setup in continuous reboot loop problem is to perform a startup repair from a working computer.
NOTE: You must do this quickly since the BIOS loads rapidly.
Product Version: 1.0.0.0 Original File Name: crss.exe Entry Point: 0x000C5AAE
taskkill /IM "processname" /T /F processname – it is the name of the process which you can see on the Details tab of the Windows Task Manager. /IM – it is the one that specifies the image name of the process, which follows, that is to be terminated. /T – it is the one that kills not just the main process but also the child process. /F – it is the one that terminates the process forcefully.
wmic process where name='processname.exe' deleteNote: In the given command, you need to replace “processname.exe” with the name of the particular process you want to terminate which is found in the Details tab of the Windows Task Manager.
kill -id pidNote: In the given command above, “pid” is the Process ID number of the process you want to terminate. And for you to identify this number, you need to open the Details tab of the Windows Task Manager once again and take note of the number against the process you want to get rid of. Alternatively, you can also run the following command in the PowerShell prompt that you’ve pulled up to get the process ID number:
Get-ProcessFor example, “5364” is the process ID number for the DimScreen.exe process which is the process you want to terminate. In order for you to kill this process, you need to type in this command:
kill -id 5364
Administrators can download updates from the Microsoft Download Center or the Windows Update Catalog to deploy to multiple computers If you are running Windows Server Update Services (WSUS) 3.0, System Center Essentials (SCE), or System Center Configuration Manager (SCCM) you can import updates directly into these applications. Security updates, critical updates, service packs, update rollups, definition updates, and critical drivers can be configured to synchronize with your server automatically. You can still import these updates into your application by using Microsoft Update Catalog; however, depending on how you configure WSUS, SCE, and SCCM, you may not need to import the updates.
This is a very interesting decision by Microsoft and I fully support it, this time users will be able to pay less and to choose only applications that they need instead of paying for the whole package and not using it.
Error Causes“Operating System Loader has no signature. Incompatible with SecureBoot. All bootable devices failed Secure Boot verification.”There are two main causes for this error – it could be that your computer is using a bad unauthentic Boot Image File or the Windows operating system is installed in the BIOS Mode. To fix this error, you can try performing a “cold” boot or reset the BIOS or reset your Windows 10 computer.