[Forum FAQ]Tips on Upgrading Windows 10 Technical Preview from Build 9841 to 9860

The new Build 9860 for Windows 10 Technical Preview has been released recently. Here, I would like to share some experience on upgrading Windows 10 Technical Preview from Build 9841 to 9860.
Tip 1: How to use Refresh option to upgrade.
Scenario
In order to upgrade to Build 9860, the new preview build should be downloaded firstly:
PC settings-> Upgrade and recovery->
Preview builds, which is as shown below.
If there are multiples PCs which are running Windows 10 Technical Preview Build 9841 need to be upgraded, you may just want to use one copy of downloaded preview build to upgrade all of them instead of downloading the new build on each PC.
Solution
If you have upgraded one PC from Windows 10 Technical Preview Build 9841 to 9860, the downloaded preview build (install.esd) can be used to upgrade other PCs. Here we can use install.esd to export the install.wim, then this intall.wim can be used as a recovery
image.
Step 1: Understand the basic information about install.esd.
Install.esd file is located at C:\ $WINDOWS.~BT\sources folder at first. When the upgrade is finished, it would be copied to
C:\RecoveryImage folder. Here is the information in setupact.log which contains information about setup actions during installation:
2014-10-28 19:03:38, Info SP Moving file D:\$Windows.~BT\Sources\Install.esd to D:\RecoveryImage\Install.esd
What’s more, the command Dism /Get-Wiminfo /Wimfile:<path_to_install.esd> is used to display the information about the file install.esd:
Step 2: Export the file install.wim.
The following command is used to export Windows 10 Technical Preview Build 9860 image:
Dism /Export-Image /SourceImageFile:<path_to_install.esd>
/SourceIndex:4 /DestinationImageFile:<path_to_install.wim> /Compress:recovery
Step 3: Copy exported install.wim to other Windows 10 Technical Preview Build 9841 computers, and set the recovery image.
For example, the install.wim has been copied to C:\image folder, the following command is used to set the recovery image:
Reagentc /setosimage /path C:\image /index 1 /target C:\Windows.
Step 4: Use Refresh option to upgrade your PC.
Go to
Update and recovery setting under PC settings, choose
Refresh your PC without affecting your files:
Note:
Applications needed to be reinstalled.
System would use the exported install.wim to refresh Windows 10 Technical Preview from Build 9841 to 9860:
Note: If you use install.esd to refresh directly, just need point the index location as 4:
Reagentc /setosimage /path C:\image /index 4 /target C:\Windows. However, install.wim is easier for deployment, such as creating bootable USB, WDS and SCCM deployment.
Tip 2: Workground to upgrade native boot VHD.
Scenario
Many users use the method native boot into VHD to test Windows 10 Technical Preview. However, there is a limitation on native boot when using VHDs:
If you boot from a VHD, you cannot upgrade the Windows version in the VHD to a newer version. This article describes how to upgrade VHD system Windows 10 Technical Preview from Build 9841 to 9860.
Solution
Step 1: Upgrade in Hyper-V.
Use Hyper-v to create a new virtual machine, and use your native boot VHD
as an existing virtual hard disk:
If booting from this virtual disk directly, it would fail to start due to lacking of boot files. You can use Windows 10 Technical Preview Build 9841 ISO file to repair the startup issue:
You can boot intosystem successfully in Hyper-v, then the upgrade process would be supported.
Step 2: Create Native Boot to VHD.
When the upgrade is finished, shut down the virtual machine, use the same way to create Native Boot to VHD:
Mount the 9860 native boot VHD file.
Use the following command to create boot entry for VHD system: Bcdboot
v:\windows (v: represents the mounted virtual disk drive letter).
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hi Arman mohseni,
From my observation, if I click download now, it would create a BITS task:
We can use following command to check:
Import-module bitstransfer
Get-bitstransfer –allusers
From the output, we can see the system account created a BITS job for transferring, under the C:\Windows\Software Distribution\download, we can get the temporary downloaded file, which is approximately about 2.5G.
After we restart, and go to C:\Windows\Software Distribution\download, the temporary file is gone.
If I click the download again, the BITS would create a new task, a new temporary file, if we compare the JobIds of the two times downloading, they are totally different.
On the other hand, if we download a windows update, the JobId would be kept, and the temporary files would be kept, too.
Alex Zhao
TechNet Community Support

Similar Messages

[Forum FAQ]How to upgrade Windows Server 2008 R2 with a GUI to Windows Server 2012 Server Core

We found that some customers willing to upgrade Windows Server 2008 R2 GUI to Windows Server 2012 Server Core recently. This article provides detailed steps to perform the upgrade.
Analysis
Upgrading from Windows Server 2008 R2 with a GUI installation to Windows Server 2012 with Server Core directly
is not supported. If you do that, you will receive the error message below(Figure 1) in Compatibility report:
Figure 1.
In these scenario, you can upgrade to Windows Server 2012 firstly. After the upgrade process is completed, you can switch freely between Server Core and Server with a GUI modes.
Produces
You can follow the steps below to perform an upgrade from Windows Server 2008 R2 with a GUI installation to Windows Server 2012 Server Core mode:
1. Upgrade to Windows Server 2012 with a GUI mode
1) Firstly, please boot into Windows Server 2008 R2 with a Windows Server 2012 installation DVD inserted.
2) Select the operating system you want to install with a GUI mode.
We can see 2 options (Server Core Installation or Server with a GUI) for each operating system version. (Figure 2)
Figure 2.
Note: Please make sure you have enough disk space on system partition. Or you will get such an error in Compatibility report.(Figure 3)
Figure 3.
After the Compatibility check, the installation will continue. It will take several minutes until upgrading is done.(Figure 4)
Figure 4.
2. Switch the GUI mode to Server Core
Method 1: Using Server Manager
1) Open Server Manager, click
Manger and select “Remove Roles and Features” to start the
Remove Roles and Features Wizard.
2) In Features,
uncheck the box next to the “User Interfaces and Infrastructure” option, and then click “Next”. (Figure 5)
Figure 5.
Now tick the “Restart the destination Server automatically if required” box, then click “Remove”. (Figure 6)
Figure 6.
Method 2: Using Windows PowerShell
There are multiple ways to remove the GUI via Windows PowerShell, we introduce the way of using the ServerManager module.
You can also run the commands in Windows PowerShell with an administrator to remove the GUI feature:
“Import-Module ServerManager”
“Uninstall-Windowsfeature Server-Gui-Shell –Restart”
or
“Uninstall-WindowsFeature Server-Gui-Shell, Server-Gui-Mgmt-Infra –Restart”
It will take a period of time to remove the GUI feature and reboot. When the system boots up, you will get into the Windows Server 2012 with Server Core mode. (Figure 7)
Figure 7.
More information:
Switch between Full and Server Core in Windows Server 2012 using PowerShell 3.0
http://blogs.technet.com/b/puneetvig/archive/2012/10/16/switch-between-full-and-core-in-windows-server-2012-using-powershell-3-0.aspx
Windows Server Installation and Upgrade
http://technet.microsoft.com/en-us/windowsserver/dn527667.aspx
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hi,
Brian is right, for mange the Server 2008r2 sp1 we recommend use the Windows 7 or 7.1 platform.
More information:
Remote Server Administration Tools for Windows 7 with Service Pack 1 (SP1)
http://www.microsoft.com/en-us/download/details.aspx?id=7887
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows To Go Device using Windows Technical Preview

I have successfully made a Windows To Go Device by the steps in this Technet forum post:
http://social.technet.microsoft.com/wiki/contents/articles/6991.windows-to-go-step-by-step.aspx
Note: I used a host machine running Windows Technical Preview already to make this device, since older versions (Windows 8/8.1) of DISM don't work for imaging Windows Technical Preview Installation.
Everything works fine. The device on which Windows To Go is running is a high-speed USB 3.0 HDD, so there is no significant performance difference. However, while updating to the new build 9860, the upgrade fails stating that you can't install it to a USB
Flash Drive.
Question 1) Does this problem has anything to do with the fact that I am NOT using the enterprise version of Windows Technical Preview, the only version which "technically" supports Windows To Go feature.
Question 2) My host machine (which I used to create Windows TP) has been updated to Build 9860. Should I use DISM to capture the image of this updated build and use it to image the WTG HDD device? Can I get detailed instructions on how to do this?

Hi G.One1,
In current time, there is no direct way to perform the upgrade, in both Native Boot to VHD and Windows To Go.
I was thinking a way to create a ISO file also, but the method would be a bit of complicated.
Here is my thought and steps.
First, if we update our Windows 10 Technical Preview for Enterprise to 9860 build, we would get a install.esd file, in Windows 8.1, here is a tool called update advisor, which would
convert the esd file to ISO file, but in Windows 10 Technical Preview, there is no such thing. So my thought is to use the install.esd to create an install.wim or bootable ISO file.
In my first thought, I want to sysprep an updated OS, but it failed without doubt. So, I choose to use Reset option. Install.esd would be recognized a compressed install.wim.
I copy the install.esd to a 9841 build OS, for example, I copy it to C:\RecoveryImage, and run
reagentc.exe /setosimage /path C:\RecoveryImage /target c:Windows /Index 1 , it cannot reset the Windows OS.
I use Reset option in 9860 build OS, when it is finished, run sysprep, it ran well, I can capture 9860 build wim file (WDS server capture or dism command). We rename it as install.wim.
Use the captured install.wim to set recovery image in 9841 build(copy install.wim to C:\RecoveryImage, and run
reagentc.exe /setosimage /path C:\RecoveryImage /target c:Windows /Index 1), 9841 build succeed upgrade to 9860 build via Reset and Refresh options.
For Windows To Go, Yes, you can use all Windows features with your Windows To Go workspace. The only currently unsupported features are using the Windows Recovery Environment and PC Reset &
Refresh. So this way is not appropriate in your situation. But here we use these steps can convert the install.esd to install.wim, and use reset and refresh option to upgrade current build.
Refresh would upgrade without losing setting and data. For your scenario, use dism to apply 9860 install.wim would be your option.
Alex Zhao
TechNet Community Support

Hyper-V Not Enabling on Build 10041 of the Windows Technical Preview

So I am running build 10041 of the Windows technical preview. I am not able to enable the Hyper-V Platform. Here are the steps:
Go to Control Panel -> Program and Features -> Turn Windows features on or off - > Select Hyper-V Platform Checkbox.
Windows will perform the install and request a restart.
While restarting, I will get the updating windows message and at about 95 % it gives me a message to the tune of "Unable to update windows" and it roll backs the changes and restarts. No Hyper-V.
Note that I can install the Hyper-V tools with out any issues just the Hyper-V Hypervisor and Hyper-V services will not install.
Anyone have any ideas?

So I am running build 10041 of the Windows technical preview. I am not able to enable the Hyper-V Platform. Here are the steps:
Go to Control Panel -> Program and Features -> Turn Windows features on or off - > Select Hyper-V Platform Checkbox.
Windows will perform the install and request a restart.
While restarting, I will get the updating windows message and at about 95 % it gives me a message to the tune of "Unable to update windows" and it roll backs the changes and restarts. No Hyper-V.
Note that I can install the Hyper-V tools with out any issues just the Hyper-V Hypervisor and Hyper-V services will not install.
Anyone have any ideas?
Can't provide an answer, but I have the same problem. I'd originally let my 9926 build, with Hyper-V installed and working, upgrade to the 10041 build. After installation things seemed OK, until I noticed I had no network connections working. They were all
still there, but I had no network access and trying to view the properties of either my physical NIC or the Hyper-V switches just gave me an error.
I tried uninstalling Hyper-V, but after doing that Windows wouldn't boot at all. It'd begin to start up, get almost to the login screen, but then die and reboot. I decided a rebuild would probably be best anyway, so I chose to do a Refresh when it offered
me the advanced repair options.
The Refresh mostly went well, the PC is running better now with a clean install, but I'm now stuck in the same situation where the Hyper-V server won't install. It installs, reboots, gets part way through configuring, then claims to fail and backs it all
out again. No real diagnostic info presented as to why.

Is Windows Technical Preview Build 9926 Last Build before Release (PC) ??

As @ Mar 14 2015 - My WIN10 build Installations (9926) no longer have "Preview Builds" option,
in Update & Recovery Menu (PC Settings)
Build 10036 announced by rumour mill...
Dell Precision 490 Desktop Intel XEON X5365 (Quadcore) x 2 Chipset X5000 321x/3221ESB Southbridge AMD Radeon HD7750 HDD ST3000DM001 3TB HDD ST2000DM001 2TB SSD OCZ Vertex 3 120GB SSD OCZ Vector3 128GB x2 RAID 0 Offline WD10EALX 1TB Barracuda 7200.10 250GB
USB 3.0 WD MyBook 1230 3TB USB 3.0 WD MyBook 1130 2TB

Microsoft Community got there first...
http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/is-windows-technical-preview-build-9926-last-build/bb0bed43-4d64-4e1b-acaa-fee158f034ce
Thanks Andre da Costa
Dell Precision 490 Desktop Intel XEON X5365 (Quadcore) x 2 Chipset X5000 321x/3221ESB Southbridge AMD Radeon HD7750 HDD ST3000DM001 3TB HDD ST2000DM001 2TB SSD OCZ Vertex 3 120GB SSD OCZ Vector3 128GB x2 RAID 0 Offline WD10EALX 1TB Barracuda 7200.10 250GB
USB 3.0 WD MyBook 1230 3TB USB 3.0 WD MyBook 1130 2TB
We only reply to questions posted in TechNet forums.
We don't go to MS Community and find out if the same question has been answered or not before we post the replies.
There is no such thing as who gets "there" first.

Adding features to Windows Technical Preview

Why serial code not work with Windows Technical Preview evalution copy Build 9879?
Add features to Windows Technical Preview and asks for serial key, two different serial key but not work.

Hi,
Where did you get the product key? Online purchase is not available at this moment (my region is set to US), and please note that the product key for "Add feature" is not the same key for activating system.
If you have any feedbacks on Windows 10 Technical Preview, please click the search botton in the left bottom of the screen, type "Windows Feedback", then submit your feedback.
Regards.
Yolanda Zhu
TechNet Community Support

Windows 10 technical preview latest build 9926 won't rise

After install cisco vpn client windows 10 technical preview latest build 9926 won't rise, only black screen and mouse arrow ?????How to fix it ?

I used the option to refresh the pc
that is uninstalled everything
except win10 OS(even
office 2013).after that
the system is started.
It is still a problem installing
cisco vpn client ..... how to solve.
Any suggestion...

Couldn't install windows technical preview on a usb flash

Hi,
couldn't install windows technical preview on a usb flash setup.
please say me the solution to this problem

Hi,
Any errors poped out? You may try to switch to a USB 2.0 port and check this issue again.
If you have DVD drive available, you may also choose to install Windows 10 through DVD, download the ISO file using this tool:
Windows USB/DVD Download Tool
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Officejet Pro K550 in Windows Technical Preview

The most recent update to Windows Technical Preview Build 9879 keeps stopping the print spooler when the Officejet Pro K550 is attached. It worked fine in the previous builds. Any ideas? I need to keep the USB cable disconnected until I want to print and then uninstall the printer each time or keep restarting the print spooler each time I want to print anything.
Thanks

Hi,
Try running Windows Update and check if any driver update is available, any drivers for the Technical Preview are only available from Microsoft Update servers.
If the issue persists, you will need to wait till an update will become available by microsoft, as a beta OS you are likley to experience this kind of issues, devices hasn't have been tested much, as well as the entire operating system.
Shlomi
Say thanks by clicking the Kudos thumb up in the post.
If my post resolve your problem please mark it as an Accepted Solution

Upgrade from build 9841 to 9926 possible from iso?

I am using windows technical preview build '9841' . I am unable to download and install '9926' from windows recovery options.
Can I download the iso and 'upgrade' to the latest 9926 build without a clean install? I do not want to loose any installed programs . Is it possible to upgrade from the iso to the new build without reinstalling everything again? Is there an option for ugrade
while installing using the .iso file?

On Sat, 24 Jan 2015 06:59:26 +0000, Carey Frisch [MVP] wrote:
Once you properly burn the ISO to a DVD, begin the upgrade while at your desktop.
There is no need to burn a DVD, just mount the ISO file using the native,
built-in mounting facility in Windows Explorer and then run setup.exe.
Paul Adare - FIM CM MVP

[Forum FAQ] How to show Windows Update in Control Panel in Clean Installation of Windows 10 Technical Preview Build 9926

Scenario
If you performed a clean installation of the new Windows 10 Technical Preview Build 9926, you would find Windows Update is only available in
Settings and is hidden in Control Panel by default. However, Windows Update is still available in Control Panel if it is an upgrade version of Windows 10 Technical Preview Build 9926.
Solution
After the comparison of the two different version, the differences is the following registry:
HKLM\SOFTWARE\Microsoft\WindowsUpdate\UX\IsConvergedUpdateStackEnabled
In clean installation version:
In upgrade version:
The method to make Windows Update show in Control Panel in the clean installation of Windows 10 Technical Preview Build 9926:
Edit the REG_DWORD value of IsConvergedUpdateStackEnabled from 1 to 0.
Applies to
Clean installation of Windows 10 Technical Preview Build 9926
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

We’ve seen a few forum posts talking about changing registry keys to alter the update experience we shipped in Technical Preview build 9926. There are a couple of reasons that we don’t recommend doing things like that.
First, the default experience is what we’ve tested across not just the Windows 10 team, but across all of Microsoft before we released it to you. That doesn’t mean that you won’t still find bugs, but it’s definitely the code that’s been most thoroughly
tested. Changing things back to older versions is risky because the combination of those old settings with the rest of Windows 10 is not something that’s been validated or supported, so we can’t predict the side effects. It’s possible that changing registry
settings related to update could cause a machine to no longer be able to get new updates or Technical Preview builds.
The other reason to avoid changing the default update experience is that a lot of update-related code is actually being re-written in order to scale across the variety of different device types Windows 10 will support. Since Technical Previews are
a work-in-progress, some code that may still be in build 9926 won’t actually ship in the final version of Windows 10 that we provide to all our customers, so trying to re-enable that code temporarily won’t provide a way to accurately assess Windows 10’s update
capabilities.
We want to hear your feedback! We’re sharing Technical Preview releases early so we can understand exactly how customers are using our software and make sure we are designing our experiences to address those scenarios. The more
specific the feedback, the more helpful it is for us – saying “I hate the new Windows Update UI” isn’t very useful, but when we see “I need to be able to tell Windows Update to grab updates from WU itself and not from my internal corporate server, so the new
Windows Update UI is painful for me”, we can actually understand what changes we could make to solve those specific problems. We can’t promise to fix everything that everyone asks for – and sometimes what one customer wants is exactly what another customer
doesn’t want – but the more you can help us understand why you want something changed, the better we can try to meet those needs.
Thanks for listening, and we look forward to hearing your responses.
http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_update/warning-disabling-the-new-windows-update-ui-may/dc846517-eca0-4960-b0ff-1eb7227223f5

Unable to upgrade or install windows 10 enterprise technical preview from windows 8.1 pro

Compaq Presario SR2034NX
windows 8.1 pro build 9600 64 bit, x64processor
I have attempted a clean install booting from a burned dvd with the iso file on it using the windows 7 USB/DVD download tool, Ive attempted to boot from a usb using rufus. Ive even attempted to just run as administrator right from the download
the setup file.
Installing via USB windows 10 opens the language screen but everything on my screen is distorted, ive tried to change my screen resolution to fix this. it did not work. Once I managed to click my way to the next screen but windows 10 asked me
for a driver to be installed and I have no idea what driver that could be.
Installed via DVD and direct setup file windows 10 opens to the making sure your pc is updated.. then it downloads and says its installing. at the moment it finished installing and restarts the next screen is black and the windows wheel starts turning
it freezes.. about every minute to five minutes it will turn a bit more.. I left my pc in this state for a full 24hours without touching it and it never finished installing.
I have tried several different builds. I even downloaded bluestacks and ran windows 10 enterprise technical preview as a virtual and I was successful doing it this way but Ive already tested windows 10 on two other desktops and a laptop of mine and im ready
to make the switch. this is my last desktop to run windows 10 and its giving me a hard time.
can someone please help me figure this out

Hi Metro1952,
I found the following link indicates that there is no official driver designed for Windows 8 or later:
Compaq Presario Media Center SR2034NX Desktop PC
http://support.hp.com/us-en/drivers/selfservice/Compaq-Presario-SR2000-Desktop-PC-series/3239110/model/3250934
So, there might be a compatibility issue.
Again, to prepare the USB installation, you need ensure that you boot from the USB device, I suggest you make a clean USB boot drive by using diskpart:
DISKPART> list disk
DISKPART> select disk x (x is the USB drive letter)
DISKPART> clean
DISKPART> create partition primary
DISKPART> select partition 1
DISKPART> active
DISKPART> format FS=NTFS QUICK
DISKPART> assign
DISKPART> exit
Then copy the all installation files to the root of the USB drive:
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Windows 10 Technical Preview Enterprise Build 9879 Product Key

Hi
Does the Windows 10 Technical Preview Enterprise 9879 uses the same product key as build 9841???

I would have been totally satisfied if the final release was B9860.
I have installed the TP on all my pc's. I have 3 desktops and a laptop that I did clean installs for on spare hard drives.
I also cloned the Windows 8.1 systems from each of them - and upgraded to Win 10 TP to see how it would handle the variety of applications I have on each.
One minor issue was that a diagnostic application I prefer to use - lost some of it's capability to display certain components like CPU specs.
The audio had been working exceptionally well up to B9860. Then I had one major issue on one of the desktops - when the audio stopped working right. Microphone audio was passed to the speaker output correctly - but NO audio
was passed from Windows Media Player or Winamp. But it did pass audio thru to the speakers from a music editing application which I use.
Even more strange was that when I moved that hard drive to another desktop which has similar motherboard - the audio works perfectly. Both have VIA audio devices.
I also installed Win10 TP Enterprise on a hard drive and had the same results as above when booted up on those two desktop pc's. Whatever evidence I could extract has been passed back to Microsoft.
On checking I find the Win10 TP and Enterprise use the same key.
Otherwise - as you say - Windows 10 is GREAT. So I can't wait for the final release.
btw: I have done about a dozen different installs and never had to enter the install key when installing any of the Win10 systems. I have the general Win10 TP B9841 ISO burned to a DVD and each install had to be upgraded to the next build available.
The Enterprise comes as B9879 and I burned that ISO to a USB3 Flash Drive. Much better performance - and re-usable. So I will not be using DVD's in future.

X-Fi Titanium on Windows 10 Technical Preview 2 (build 9926) - anyone made it work?

As in title - was anyone able to make this soundcard work on latest build of windows 10? Installing windows 8.1 driver on previous technical preview was making the card work, installing on current build is close to pointless as card is not working properly and creative control panel can't start as it can't find device.

Originally Posted by jmacguire
pmc64:
While I understand your frustration, there is simply no reason for Creative to make drivers for this card any longer. The fact that Windows 8 drivers were made was surprising, but Windows 10? I just do not think that would happen. It is simply not economically feasible, regardless of any "good will" that it may create. Good will does not keep the lights on if you know what I mean.
That had better not be an official response from this company, because the backlash may well be more than they can bear.
Yea, we'll update our cards if we have to, but it won't be to another creative product.
In their case, "good will" is the only **** thing that will keep the lights on...

ComputerName in Unattend.xml ignored by Windows 10 Technical Preview [all builds]

Since I was not successful in creating an Unattend.xml with
Windows 10 Technical Preview ADK I modified the one from Windows 8.1. This works with exception of
<ComputerName>MYW10PCNAME</ComputerName>
I do get an auto-generated PC name instead.
The process is, that the Unattend.xml is copied into Panther folder after image build incl. sysprep.
Can someone post an Unattend.xml that is working for Windows 10 Technical Preview?
I will try to post this in feedback app.

Hi,
It seems like there is a problem with Windows 10 deployment. Firstly, please post this phenomenon to Windows Feedback.
In my opinion, it is probably Windows 10 itself problem, I would make a deep research with this problem, hoping there is some progress.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

[Forum FAQ]Tips on Upgrading Windows 10 Technical Preview from Build 9841 to 9860

Similar Messages

Maybe you are looking for