Blog

Follow the steps below:

• Press Windows logo key + X to bring up the power menu in Windows 10

• Now, Press A
• Click on Yes, when prompted (This opens up an elevated command prompt)
• Type in Regedit

o

• Now, Click on Computer

• Go to the File menu & Click on Export

• Browse to your desired backup location
• Type in a desired backup name
• Make sure to select ALL at the bottom
• Click on save

If you have any questions or comments, please use the comments box.

This post helps you create a virtual switch in Windows 10. A virtual switch is used to enable the virtual machines to communicate with your physical network. A Virtual switch is mandatory for any Virtual Machine to communicate with the network, so it’s a bridge between your VM & Network. Below are the steps to create a network switch.

• Open up the Hyper-V manager
• 
• Type Hyper-V manager in the start screen | Start menu
• Now, Click on the server name on the Left hand side pane
• 
• Then, Click on Virtual Switch Manager
• Now, Click on New Virtual network switch
• 
• Click on External
• Click on Create Virtual Switch
• Now, Give a name to your switch
• Click on Apply
• 
• You will get a notification like the one shown below
• 
• Click on Yes
• Changes will be applied
• To check whether your virtual switch is working or not,
• Right Click, the Network icon in your taskbar
• 
• Click on Open Network and Sharing Center
• 
• You should see the name of your virtual switch listed here.

Hope this post helps, your comments & suggestions, if any, can be shared through the comments section.

After reading this post you will be able to restore a checkpoint that you made earlier. Checkpoints are a feature of Windows 10 hyper-V, where you can very conveniently undo the changes made to a Virtual machine. It’s something like system restore, but deals with a rather different model, known as standard checkpoints & Production checkpoints. Learn how to create a checkpoint in Windows 10 using this post. Now, below is the method to Restore this checkpoint:

• Open Hyper-V manager
• Go to the Start menu | start screen
• Type Hyper-V manager
• 
• Now, Select the server from the left hand pane
• Start any of your VM that you previously created a Checkpoint on
• Now,
• Click Action menu at the top
• Click on revert
• Click on Revert
• 
• By doing this your VM will now revert to the state in which you created a checkpoint
• 

This post concentrates it’s focus on an issue that comes when either you have a computer that’s running Windows 10 RTM (Build 10240) or you have upgraded your computer to Windows 10 version 1511 (Build 10586). In both of these scenarios, you might receive an error “Namespace ‘Microsoft.Policies.Sensors.WindowsLocationProvider’ is already defined as the target namespace for another file in the store.  when you try to run gpedit.msc & try to click on either User or computer configuration. You might not get this issue if you are upgrading from Windows 7, Windows 8.1 directly to Windows 10 version 1511 & skipping Windows 10 RTM. I recently faced this issue when visiting a Microsoft conference at Hyderabad and thought to post a solution to it.

The screenshot of the example looks like this:

The error reads:

Namespace ‘Microsoft.Policies.Sensors.WindowsLocationProvider’ is already defined as the target namespace for another file in the store.
File
C:\WINDOWS\PolicyDefinitions\Microsoft-Windows-Geolocation-WLPAdm.admx, line 5, column 110

This usually happens when the the files “Microsoft-Windows-Geolocation-WLPadm.admx” & “LocationProviderADM.admx” present in C:\Windows\PolicyDefinitions\ and “Microsoft-Windows-Geolocation-WLPAdm.adml” and “LocationProviderADM.adml” present in C:\Windows\PolicyDefinitions\en-us gets rewritten or corrupted during up gradation.

Below are the steps to Fix: Namespace error with gpedit.msc Windows 10

Solution: Delete these files mentioned above

First Step: Taking ownership of all these files:

takeown /F ” C:\Windows\PolicyDefinitions\Microsoft-Windows-Geolocation-WLPAdm.admx” /A  

takeown /F ” C:\Windows\PolicyDefinitions\en-US\Microsoft-Windows-Geolocation-WLPAdm.adml” /A

takeown /F ” C:\Windows\PolicyDefinitions\LocationProviderADM.admx” /A

takeown /F ” C:\Windows\PolicyDefinitions\en-US\LocationProviderADM.adml ” /A

• Now, Change permissions
• Go to C:\Windows\PolicyDefinitions
• Find the file LocationProviderADM.admx and Microsoft-Windows-Geolocation-WLPAdm.admx
• Right Click the file & Click on Properties
• Go to the security tab

• Click on Administrators
• Click on edit
• Now, again click on administrator
• Check the checkbox that says full control
• Click on Apply and ok
• Now, repeat this step for the remaining three files
• Now, delete all four files
• Done
• Try opening gpedit.msc

Hope this helped you, if you have any questions or suggestions, please feel free to write to me.

Live Streaming[schema type=”event” evtype=”Event” url=”http://build.microsoft.com” name=”Microsoft Build 2016 Live” description=”Microsoft Build 2016 conference live” sdate=”2016-03-29″ stime=”12:00 pm” edate=”2016-03-31″ duration=”12:00″ ] Microsoft Build 2016 Live Conference is here !  After Q1 being at its end phase, Google announcing Android N & Apple Launching a new smartphone, Microsoft had to bring something to the table. Windows 10 has been amongst the biggest of software launches for Microsoft, and with Windows 10 Mobile coming to Windows 8.1 based smartphones, a new more productive era of deliverance is taking shape.

Microsoft is expected to deliver uniformity & unifying platforms. This can be seen with recent events such as the openness event. Build 2016 is expected to involve something of this sort. With that new & more interactive live tiles are expected to be featured.

Watch the Build 2016 conference stream live here from here : Troubleshoot Windows