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]

Similar Messages

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

[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

Lync screen sharing doesn't work in Windows 10 Technical Preview (9879 Build)

Why Lync screen sharing doesn't work in Windows 10 Technical Preview?
It works well Windows 8.1, but why not in Windows 10?

Hi PriTeddy,
Thanks for your feedback.
As Paul Adare said, Microsoft has noticed such issue, they are listed in following blog:
http://blogs.windows.com/bloggingwindows/2014/11/12/new-build-available-to-the-windows-insider-program/
Some known problems:
As with the last build, you’re getting hot-off-the-presses code which means there are a few issues. We’ll be publishing WU updates shortly to fix the first two, but the remainder will not be fixed for 9879.
•In some cases you may get a black screen when trying to log-in or unlock. The only option is to hold the power button to hard reboot.
•You will be unable to connect to Distributed File System network locations.
•Some systems may see disk growth of 20GB+ due to driver install duplication. On systems with low disk space this can block setup and cause a rollback to the previous build.
•Skype calls will disconnect and Music will stop playing if those apps are minimized.
•There are several known issues with screen sharing with Lync.
Let’s wait for next builds.
Alex Zhao
TechNet Community Support

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

About the error: "The account is not authorized to login from this station" when you access NAS devices from Windows 10 Technical Preview (build 9926)

Scenario:
With the release of Windows 10 Technical Preview (build 9926), some users may encounter an error message of “The account is not authorized to login from this station” when trying to access remote files saved in NAS storage. In
addition, the following error log may also be found via Event Viewer:
Rejected an insecure guest logon.
This event indicates that the server attempted to log the user on as an unauthenticated guest but was denied by the client. Guest logons do not support standard security features such as signing and encryption. As a result,
guest logons are vulnerable to man-in-the-middle attacks that can expose sensitive data on the network. Windows disables insecure guest logons by default. Microsoft does not recommend enabling insecure guest logons.
Background:
The error message is due to a change we made in Windows 10 Technical Preview (build 9926) which is related to security and remote file access that may affect you.
Previously, remote file access includes a way of connecting to a file server without a username and password, which was termed as “guest access”.
With guest access authentication, the user does not need to send a user name or password.
The security change is intended to address a weakness when using guest access. While the server may be fine not distinguishing among clients for files (and, you can imagine in the home scenario that it doesn’t
matter to you which of your family members is looking at the shared folder of pictures from your last vacation), this can actually put you at risk elsewhere. Without an account and password, the client doesn’t end up with a secure connection to the server.
A malicious server can put itself in the middle (also known as the Man-In-The-Middle attack), and trick the client into sending files or accepting malicious data. This is not necessarily a big concern in your home, but can be an issue when you take your
laptop to your local coffee shop and someone there is lurking, ready to compromise your automatic connections to a server that you can’t verify. Or when your child goes back to the dorm at the university. The change we made removes the ability to connect
to NAS devices with guest access, but the error message which is shown in build 9926 does not clearly explain what happened. We are working on a better experience for the final product which will help people who are in this situation.
As a Windows Insider you’re seeing our work in progress; we’re sorry for any inconvenience it may have caused.
Suggestion:
You may see some workarounds (eg. making a registry change restores your ability to connect with guest access).
We do NOT recommend making that change as it leaves you vulnerable to the kinds of attacks this change was meant to protect you from.
The recommended solution is to add an explicit account and password on your NAS device, and use that for the connections. It is a one-time inconvenience,
but the long term benefits are worthwhile. If you are having trouble configuring your system, send us your feedback via the Feedback App and post your information here so we can document additional affected scenarios.
Alex Zhao
TechNet Community Support

Hi RPMM,
Homegroup works great in Windows 10 Technical Preview (9926 build), when I invited my Windows 10 Technical Preview (9926 build) joined in HomeGroup, I can access the shares smoothly:
My shares settings is like this:
Alex Zhao
TechNet Community Support

Windows 10 technical preview installation has failed

Hi,
I currently use Windows 10 build 9860 on my computer and in another partition of my hard drive I have windows 8.1
Today I was trying to update my build trough the update and recovery>preview builds, but I was getting this error message: "Failed to install the new build, please try again later. 0x8024200D"
After that, I tried to download the offline .iso of the new build and running the setup, every was looking fine but when the installation got to 25% it came back to my desktop and a message appeared: "windows 10 technical preview installation has failed"
Any way that I can solve this?
Thanks

Hi,
I tried a bunch of different steps:
- Do a clean boot
- Use command WSReset.exe on run box
- Command prompt:dism.exe /online /cleanup-image scanhealth and restorehealth(When i use restorehealth gives me this error:0x800f081f)
- Create a new admin user and try to install update
- rename softwaredistribution
- Command prompt: powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\WinStore\AppxManifest.XML
None of this worked so far for me.
I went to C:\$Windows.~BT\Sources\Panther\setuperr.log and got this:
2015-04-03 01:56:15, Error DU DU::CDUSession::Initialize: Failed to begin IUpgradeInternalSession. hr = 0x80004002[gle=0x0000007f]
2015-04-03 01:56:19, Error CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session[gle=0x0000007f]
2015-04-03 01:57:05, Error DU DU::CDUSession::Initialize: Failed to begin IUpgradeInternalSession. hr = 0x80004002[gle=0x0000007f]
2015-04-03 01:57:24, Error SP pDUSearch: DUSearch failed. hr = 0x80070057
2015-04-03 01:57:24, Error SP CDownloadDUUpdates::DoExecuteInternal: Failed to search for updates. hr = 0x80070057
2015-04-03 01:57:24, Error SP CSetupPlatform::DownloadDynamicUpdates: Failed to download updates. Error: 0x80070057[gle=0x00000012]
2015-04-03 01:57:24, Error MOUPG DUImage: Failed to execute DUImage FOD search and download [0x80070057][gle=0x00000012]
2015-04-03 01:57:29, Error SP pDUSearch: DUSearch failed. hr = 0x80070057
2015-04-03 01:58:43, Error SP pDUSearch: DUSearch failed. hr = 0x80070057
2015-04-03 01:58:43, Error SP CDownloadDUUpdates::DoExecuteInternal: Failed to search for updates. hr = 0x80070057
2015-04-03 01:58:43, Error SP CSetupPlatform::DownloadDynamicUpdates: Failed to download updates. Error: 0x80070057[gle=0x00000012]
2015-04-03 01:58:43, Error MOUPG DUImage: Failed to execute DUImage LangPack search and download [0x80070057][gle=0x00000012]
2015-04-03 01:58:44, Error CONX Failed to get class data from printer 80070057
2015-04-03 01:59:13, Error CONX Unable to get message handle 80092009 c:\windows\system32\drivers\pltgc.sys
2015-04-03 01:59:14, Error CONX Unable to get message handle 80092009 c:\windows\system32\drivers\tapoas.sys
2015-04-03 01:59:36, Error ConX::Compatibility::CActionT<5,struct ConX::Compatibility::NoParameters>::Invoke: Successfully persist data.
2015-04-03 02:02:47, Error SP CSetSafeOSBootCommand::DoExecute: Failed to set the boot app $WINDOWS.~BT\Sources\SetupPlatform.exe. hr = 0x80070003[gle=0x00000003]
2015-04-03 02:02:47, Error SP Operation failed: Set safe OS boot command. Error: 0x80070003[gle=0x000000b7]
2015-04-03 02:02:47, Error MOUPG MoSetupPlatform: ExecuteCurrentOperations reported failure!
2015-04-03 02:02:47, Error MOUPG MoSetupPlatform: Using action error code: [0x80070003]
2015-04-03 02:02:47, Error MOUPG CDlpActionImageDeploy::ExecuteRoutine(322): Result = 0x80070003
2015-04-03 02:02:48, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Execute(441): Result =
0x80070003
2015-04-03 02:02:48, Error MOUPG CDlpTask::ExecuteAction(3218): Result = 0x80070003
2015-04-03 02:02:48, Error MOUPG CDlpTask::ExecuteActions(3372): Result = 0x80070003
2015-04-03 02:02:48, Error MOUPG CDlpTask::Execute(1630): Result = 0x80070003
2015-04-03 02:02:51, Error MOUPG CSetupManager::ExecuteTask(1710): Result = 0x80070003
2015-04-03 02:02:51, Error MOUPG CSetupManager::ExecuteTask(1673): Result = 0x80070003
2015-04-03 02:02:51, Error MOUPG CSetupManager::ExecuteInstallMode(695): Result = 0x80070003
2015-04-03 02:02:51, Error MOUPG CSetupManager::ExecuteDownlevelMode(353): Result = 0x80070003
2015-04-03 02:05:32, Error MOUPG CSetupManager::Execute(204): Result = 0x80070003
2015-04-03 02:05:32, Error MOUPG CSetupHost::Execute(387): Result = 0x80070003
I have no clue what to do next, now my windows build is saying that will expire 04/15.
Any ideas?
Thanks

Iconia 700P and Windows 10 Technical Preview Problems

I've had mixed success installing the Windows 10 Technical Preview (64-bit) on my Iconia 700P. The first few iterations worked fairly well, but around build 9943, things went terribly wrong, and the machine would not boot. After a while (and a few peripheral purchases), I managed to restore Windows 8.1 from an Acronis recovery image. I downloaded the most recent "stable" build (10030, I think) before I signed up to reserve a copy of Windows 10. It installed fine from a DVD, but things went really downhill once we got to the settings portion of the installation. After rebooting a couple times during the process, the touch screen would not work at all (nor would the bluetooth keyboard). A USB mouse allowed me to click on the screen, but the tablet shut down every time I clicked on Continue. Has anyone had success installing the WIndows 10 Technical Preview on an Iconia 700P? I searched the forum, but couldn't find anything with the Iconia 700/WIndows 10 combination. Thanks!

I have an acer w700 now running windows 10 pro, (upgraded from 8.1 pro). The only issue i found was that after upgrading, i would get the following error on booting the system; "Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.
The wait operation timed out. (Exception from HRESULT: 0x80070102)." I too thought that this was a Net Framework 3.5 problem, but in fact, it is an Acer problem.................. i found a solution to resolve this; Go into your Task Scheduler (by using Windows search). The Task Scheduler runs applications according to a schedule. The MEMS application is crashing Windows 10 (since it is doing Windows 7 related things). In the Task Scheduler Manager, go to the Task Scheduler Library and find MEMS_Schedule. Right click on that line and left click on Disable. Now restart your computer. This is an Acer issue, and until Acer issues an update, the MEMS_Schedule needs to be kept disabled. If Acer ever gets around to issuing an update for this, then you can re-enable the MEMS_Sschedule, the same way as diasabling it. Other than this annoying issue, the W700 runs very well under Windows 10...........so far.............

Windows 10 technical preview problem with lumia 730, wifi is not working and how to rollback to windows 8.1 please help

I installed windows 10 technical preview on my lumia 730 and now iam facing problem
1) unable to connect wifi
so please help me how to roll back to windows 8.1
in the forums it was written that if u have windows recovery tool then it is possible , but iam not able to find windows recovery tool.
Please help me my mail id [email protected]

so please help me how to roll back to windows 8.1
http://windows.microsoft.com/en-us/windows/preview-backup-restore

Unable to install Essentials Role on Windows Server Technical Preview (VHD)?

Hi
Having a problem trying to install Essentials Role on Windows Server Technical Preview (VHD)
After reboots, AD installs, I get Configuration encountered some issues in Results wizard.
Updating an preparing your server... 68% completed then it fails with following error.
"An error occurred while configuring Windows Server Essentials. Please try again."
Trying again same error.
Anyone able to get this installed?
TIA

Hi,
I did the same test without any problem.
You could try it again to check the result.
If it does not help, please refer to this kb article:
http://support.microsoft.com/kb/2914651
Regards.
Vivian Wang

I can't install Windows 10 Technical Preview in Dell Inspiron M5030

Hello everyone.
I have a big problem when installing the Windows 10 Technical Preview, everything goes well until the moment that says "getting devices ready XX%" after this the screen turns black, which I had already happened when installing Windows 8.1 . I have
Windows 8 Pro and gave me problems to install, but with these two versions of Windows I always throws this error. Right now what interests me is to have installed Windows 10 Technical Preview to be developing some applications we have had in mind
a few colleagues and I, but I have not managed to install it. I have to turn the laptop to use it again, and when you start telling me "restoring your previous version of windows" And once again normally on, send me a message saying "We Could
not install Windows 10 Technical Preview" and send me the error code 0xC1900101 - 0x30018.
HELP!
I urgently need to have installed this version of windows.

Hi Domeck98,
This kind of issue is mostly caused by the driver compatibility issue during upgrade.
And it’s hard to find the culprit from installation log. The error code is sent by the setupact.log.
For a better method to test the 9879 build, it is recommended to perform a clean install in your case:
Here is the link to download the 9879 build ISO.
http://windows.microsoft.com/en-us/windows/preview-iso-update?os=win10
We can burn it to DVD media or use it create bootable USB drive.
Alex Zhao
TechNet Community Support

Can i use windows 10 technical preview for commercial purpose like developing projects in visual studio

can i use windows 10 technical preview for commercial purpose like developing projects in visual studio

No, Windows 10 Technical Preview is for testing and evaluation only , in addition it is not the final version of Windows and it is strongly recommended to use it for testing
not production.

Installing administrative tools for Windows 10 Technical Preview for Enterprise

At first I was upgrade my Windows 8.1 to Windows 10 Technical Preview for Enterprise every things done will then
I try to install administrative tools for windows 10 technical preview for enterprise I found the .msu file from Microsoft website but when I tried to install it, it gives me the following error:
Windows Update Standalone Installer
installer encountered and error: 0x8024001d
is there anyone to help me regarding above issue.
Thanks
Zelgay Kunari

Hi zelgay,
This is my result:
From your error code, it seems this is relate to your windows update, please use following command to fix corrupted files:
DISM.exe /Online /Cleanup-image /Restorehealth
In the meantime, you can delete temporary update files in the SoftwareDistribution folder:
Stop Windows Update service.
Open File Explorer.
Double-click the local hard disk where Windows is installed, typically drive C.
Double-click the Windows folder, and then double-click the
SoftwareDistribution folder.
Double-click the DataStore folder to open it, and then delete all files and folders in the folder.
Note If you're prompted for an administrator password or confirmation, type the password or provide confirmation.
Click the Back button. In the SoftwareDistribution folder, double-click the
Download folder to open it, and then delete all files in the folder.
Restart Windows Update service.
Alex Zhao
TechNet Community Support

Windows Server Technical Preview - RDS - RemoteFX 3D

Hi Windows Server Team,
I am having an issue with the Windows Server Tech Preview and Remotefx 3D. I installed the RDS role and have it all configured with no problems. I loaded a VM of Windows 10 Enterprise Tech Preview. It works fine, however when I activate the RemoteFX 3D on
that virtual machine. It then just shows a black screen in my Hyper-V Manager and just stays hung on the black screen. I have been working with RDS and RemoteFX 3D since the Windows 2008 R2 days and have never had this problem at all. When I try to Shut down
the VM it stays hung when I try to Turn Off the VM it stays hung. I am forced to reboot the server and when it comes back up it still just shows a Black screen for the Windows 10 Enterprise VM with RemoteFX 3D turned on. I really wanted and was interested
in testing the new OpenGL features and other ehancements that have been mentioned with this version of RDS and remotefx 3d. I also noticed that Gen 2 VM's now also support the RemoteFX 3D features and even tried to create a Windows 10 Enterprise as a
Gen 2 VM but I have the same problem. My server is a Dell PowerEdge R720. Thanks and I look forward to your reply and can hopefully get this working.
Regards,
Robi Rodriguez

Hi,
Thank you for posting in Windows Server Forum.
Initially we need to check whether the device is supported for latest version of features available. To use new feature available with Windows Serer Technical Preview we need to see that device supports the latest available OS. Please go through
this article for information. You can contact Dell for further information whether it
still have any updates for Windows Server Technical Preview.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

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

Similar Messages

Maybe you are looking for