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.

Similar Messages

Windows 10 technical preview.I have a product key but i can't activate it

I installed Windows 10 technical preview,i have the activation key but it is not accepted

this worked for me, as earlier posted by JonRohrich
1. Open Administrative command prompt (Windows key+x > A)
2. Type: SLUI 3
3. Enter the product key Microsoft provided for recovery scenarios: PBHCJ-Q2NYD-2PX34-T2TD6-233PK

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

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.

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...

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.

[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

Error 0x80070050 while updating Windows 10 TP Enterprise Build 9926

Hello. I'm currently using Windows 10 TP Build 9926.
Windows Update & Recovery tool indicates that there is new build of Windows 10 TP (Build 10041). Also there is update for Windows Defender (1.193.3002.0). But when I'm trying to install them process stop with error 0x80070050. Any suggestions pls?
Thank you in advance

Hi,
@ ALF_er, this version is for Windows 10 Pro Technical Preview 10041 build, it is recommended to perform a clean install, if you need the enterprise version for test, here is a workaround:
Forum FAQ] How to use Windows Imaging and Configuration Designer to upgrade from Windows 10 pro to Enterprise Version
https://social.technet.microsoft.com/Forums/en-US/c91fe33d-5097-46d4-81b1-57e36ca31409/forum-faq-how-to-use-windows-imaging-and-configuration-designer-to-upgrade-from-windows-10-pro-to?forum=WinPreview2014Setup
@ david hk129, yes, currently, there is no 10041 build Enterprise ISO release, we may need wait for a short time.
Regards,
Alex Zhao
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

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

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]

Error 0x80248014 on Windows Update on Windows 10 Technical Preview Enterprise beta build 9926.

Hi
As I download the new ISO and do a software Windows Updates.
I cannot seems to get any software updates at my end. Windows update cannot find any updates for Windows Defender.
My latest Windows 10 Technical Preview version 9926 cannot seems to find any software updates.
I keep getting this error.0x80248014!
I keep getting this error since I have the first Beta Build 9841 and 9879. I did not have the download of 9860.
I wonder there is a missing Windows Update at the Control Panel.
I have to search all over the place where is the Windows Update??? The GUI is very confusing for a First Timer like me!
See my screen capture.

mrdbeta,
Click the Retry button > if you have a Windows defender Update available, it will show up on the list together with a new build such as 9935 Professional. (See my screenshot at the end of the post.)
The system will start installing and when it finishes, it will give you the same error message. That's OK. It shows the error message because it is unable to install the new build which is NOT applicable to
us, the general users. Those new builds, 9931, 9932, 9934, and lately 9935 are meant for MSFT only.
Click Advanced options > click View your updates history. Your most recent Windows Defender update should be listed. If yes, you are OK. Nothing to worry about.
MS is well aware of the mistake. They will get it fixed soon. Please read the excerpt below from Inside Hub......
Windows Insiders who have installed KB3035129 may see reports in the Settings app under Update & recovery that a new preview build is available. Attempts to download the new build result in Error 0x80246017.
KB3035129 included a code change which unintentionally had the side effect of changing targeting for builds, allowing builds that are exclusive to Microsoft employees to appear available. No new builds are available which are newer than 9926 at this point.
We will issue another update shortly to correct the issue and ensure that Windows Insiders are able to successfully get the next build which is made available to you. We apologize for the confusion and thank you for your continued participation
and feedback.
***** In the web, there is a registry modification dealing with this issue. I would suggest that you just wait for MS to sort it out. If you want to try the registry hack, google for it. Use it at your own risk

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...

Windows 10 PreRelease Build 9841; Product Key??

Dear All,
I just installed Windows 10 build 9841 into a virtual session in preparing to see what is what; no issues there! I was looking to add functionality or features; is this not available in this edition?
Also the product key associated PBHCJ-Q2NYD-2PX34-T2TD6-233PK, is not valid to add features, any idea on what we should use?
Thanks
Rich

They'll help you over here.
Windows 10 Preview forums on Microsoft Answers
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

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]

Windows 10 Technical Preview Enterprise Build 9879 Product Key

Similar Messages

Maybe you are looking for