Blog

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

This post will help you with a unique 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. A standard checkpoint saves the VM state with all open & unsaved applications. In a production checkpoint the system state is saved & no application data is saved. Below is the method to create checkpoints.

• Go to Start menu | Start screen
• Type Hyper-V manager

• Click on the server name in the left hand pane
• Select the VM you wish to make a checkpoint on
• Click on Action menu at the top
• Click on Checkpoint
• Now, Windows will ask you for a name
• Give any convenient name
• Click on Yes

• After the Completion, you will het a message as shown below

This post will help you setup Hyper-V in Windows 10 Technical Preview | Insider Preview. In the last post I wrote, I outlined the steps to enable Hyper-V in Windows 10 TP. Now after you have enabled Hyper-V, its time to use the Hyper-V manager to setup Hyper-V and personalize it to match your settings. Remember, First thing to check is that your Computer BIOS settings for Hardware Virtualization are set to enabled.

Now, to launch Hyper-V manager:

• Type Hyper-V in the start screen | Start Menu
• 
• Select, Hyper-V manager from the listed options.
• Now, Click on the Machine ( server ) name in the left hand pane, as indicated in the screenshot below
• 
• This will list all the associated options of this particular server within your server list.
• Now, if in case, there are no servers listed in the left hand
• 
• Click on, Connect to a server
• 
• Click on Local Computer,
• Click Ok
• Now,
• Look at the options displayed on the right hand side pane.
• To change a setting, click on any one of them
• To start with, Click on Hyper-V settings
• 
• Here, You can easily set the Paths for your VHD ( Virtual Hard disk files ) & VM ( Virtual machines )
• Change them to your necessity or liking.
• After this, Add your Old VMs or setup a new one.
• Follow this Post ( How to add a new VM in Windows 10 )

This post will help you enable Hyper-V in Windows 10 Technical Preview / Insider Preview. Hyper-V is a well known virtualization service offered by Microsoft in its Operating system software. Hyper-V continues to provide its feature enriched and stable virtualization platform in Windows 10 as well. Follow the steps below to enable Hyper-V in Windows 10.

Check the Basics

Note: Make sure that Virtualization is Enabled In your computer’s BIOS.

• Go to the Start menu or start screen
• Type Programs & features
•  
• Click on Turn Windows Features on or off
• Now, Check the box saying Hyper-V as indicated in the screenshot below
• 
• Press OK
• 
• Windows will install Hyper-V & at the end will ask you to Restart your PC
• 
• Once you restart your PC, Windows will setup Hyper-V for you.

Hope this helps. Please use the comment section below to share your thoughts & feedback.