Windows 10: ** Help ** Unable to create account on install of Windows 10 10041

http://windows.microsoft.com/en-us/w...so-update-1503

 

What a strange statement! Self made ISO from the ESD is exactly the same, to the smallest detail. Please check your facts.

 

Sorry Kari but I used your files when they were posted and converted three ESDs.
I had three un-bootable ISOs.
I downloaded the ISOs from the source I posted , burned them to DVD, and did a clean install on a 32 bit and a 64 bit machine without incident.
I speak not from facts but from my own experience,

 

The tutorial tells how to create an ISO from the ESD located on your own computer. ESD file exists if you did an upgrade to build 10041.

Later on we learned that MS published direct download links to ESD files, whic I re-posted in the tutorial in this post. In the same post I told that the tool in my tutorial does not work with these ESD files, that you should use another decrypter with them. The tool mentioned in the tutorial only works with the ESD file created on your own computer when you upgrade from an earlier version of Windows or from an earlier build of Windows 10.

The ESD file is nothing else than decrypted and compressed ISO, to save download bandwidth. The tools, older one in my original tutorial and the newer one told in the post with direct links to downloadable ESD files work for 100% sure. Any error in creating an ISO can only be either a user caused error due not following the instructions to the letter, a bad download, an error iun burning the ISO or such.

If the ESD file is not damaged, and if the user follows the instructions, the ISO images created from the ESD files are to the finest detail exactly the same than the downloadable ISO images directly from Microsoft.

This is a fact.

 

I agree!
If everything is done correctly, the files are not corrupt, the decryptor is not corrupt etc. the ISO should be perfect.
BUT, mine wasn't.............. three times!
The two ISOs from Microsoft, were burned to DVD with Imgburn, the burns were verified, and then used to clean install on the same two machines that wouldn't boot from the files you posted.
I prefer the MS ISOs.............. no if'ns!
UP and running.
Working fine.
Kari, I have the utmost respect for you and your talents but that project didn't go well. You might scroll through the threads, General Discussion, Tutorials, etc, surrounding that conversion project. IMO there were other posts describing problems that could easily have been related to those files.
Just a thought.......

 

Hi,

I was experiencing the same problem with Windows 10 build 10041.
I've read all te posts in this thread, and you guys are extremely helpful, but unfortunately none of this worked for me.


After some more googling I found this post bellow and it worked just fine to me. I hope it helps someone if nothing more is working.

 

*Tongue I was able to get by the 'Create Local Account Error' by doing the following: *Tongue


1. Install 9926 using ISO
2. Skip Network connection setup
3. Customize or Express Settings(Your choice)
4. Create Local Account
5. After Windows setup completes: reboot, no settings changed
6. Login with Local Account
7. Open Windows Explorer and find ISO install media and click Setup for 10041
8. Follow normal install options as you would during downloaded upgrade.
10. At the Welcome Back screen login with Local Account.
11. Skip Network connection setup.
12. Customize or Express Settings(Your choice)
13. After successful login reinsert USB Setup drive and reboot again.
14. Get to Custom: Install Windows only (advanced)
15. Delete the OEM (Reserved) partition.
16. Click 'X' in upper right corner to exit and reboot.
17. Insert USB with Hirens.BootCD.15.2 and reboot.


Use Hirens.BootCD.15.2 to boot and then delete the following directories created with upgrade:
C:\EFI
C:\RecoveryImage
C:\Windows.old


18. Reboot then go to Disk Management and then Extend Volume 'C' to regian the ~450md of space if you want.
19. Reboot again and enjoy Windows 10 Build 10041.

 

Glad you finally got it installed SkyNet3, now lets just hope your computer doesn't become self aware *Wink

 

I hope it does then it can load and upgrade itself. lol

 

C:\EFI is created by clean install of 10041 (even if you do a BIOS install). Not sure what (if anything) it is for though.

 

I renamed C:\EFI to C:\x-EFI without issue.

I have a legacy BIOS machine though.

I think it is an install error, the EFI folder on the install media got copied to the wrong place - I could be wrong, but I don't have UEFI to test that theory.

 

UEFI-Based Computers

When you deploy Windows® to an EFI-based or UEFI-based computer, you must format the hard disk drive or other persistent storage device that includes the Windows partition by using a GUID partition table (GPT) file system. Additional drives might use either the GPT or the master boot record (MBR) file format.
A GPT-based drive might include the following partitions:

• An EFI System Partition (ESP)
  
  Each bootable drive must contain an ESP. The computer boots to this partition.
  
  For Advanced Format Generation One (4-KB-per-sector) drives, the minimum size of this partition is 260 MB.
  
  For earlier 512-byte-per-sector drives, the minimum size of this partition is 100MB.
• A Microsoft® Reserved Partition (MSR)
  
  We recommend that you add an MSR to each drive for disk management. The MSR is a reserved partition that does not receive a partition ID. It cannot store user data.
  
  The size of an MSR partition is 128 MB.
• Up to 128 primary partitions
  
  You can use primary partitions to store files and utilities.

Source
Understanding Disk Partitions

 

OK, I am still having problems with this build 10049 and the Local Account creation. I think however I have figured out what is causing the issue, now I just need to figure out how to correct it. I have attached screen shots. The first two are on a machine that I am having problems creating a local account on. with anything 10031 or later. The second two are on a machine that is working fine. Notice the TCPIP settings on the machine that is having problems are grayed out at the properties field. I fact the whole stack configuration looks different. In build 9926 the machine that I am having problems with look like the second set of screen shots and I can configure. Puzzling!!!*092

 

Here is just another piece of info about this debacle. I can remove the hard drive and install it into another Laptop then install Windows 10 Build 10049 and create a local account. Shutdown other Laptop and put hard drive back into the machine that I was having problems with and it boots just fine. I then can login with Local Account and create other Local Accounts with no problem. It just keeps getting more and more puzzling!!! *really

 

This part is no surprise. Win 10 uses a generic key and drivers. It will run on any machine as long as the specs allows it (32 or 64 bit). Now if you install 3rd party drivers manually, that's another story.