I currently have Microsoft on Live chat about my activation issue (they took control of my machine and have now activated Windows - it looked like he typed in another product code but someone he blocked the screen so I couldn't see what he typed in. I then said if I was to do a clean install again on my machine would I have the same issue - his reply was:- If you were to do a clean install of Windows 10 Anniversary edition then I would have to buy a new product key, I then stated that I upgraded my Windows 8 Pro to Windows 10 Pro and didn't have any activation problems before so why should I have problems now......He just keeps on repeating the fact that it's because its the anniversary edition!!
Format an USB thumbdrive FAT32 and extract the iso to it, now you have a bootable (UEFI & Bios) usb drive.
Please send me the link to download this iso file: pl_windows_10_enterprise_version_1607_updated_jul_2016_x64_dvd_9053882.iso Thank you so much.
Same question has been bugging me since Win10 was released. When they made the browser a Modern app I thought the reason was to have it in the Store like all other apps, but can't understand why they do it this way. It means only when Win10 gets a cumulative update then Edge is also updated, whereas being an app it should not be any longer connected to the OS' update schedule. What new nonsense is this? Unfortunately not all legacy BIOS-only systems can boot from a USB stick with just the ISO contents extracted to it.
No one expects you to wade through this monster thread but it's not difficult really! At least read the OP - then you would have seen a link to this post that keeps being updated with Enterprise ISO's. The logical thing to do is bookmark that post and keep checking it.
Why don't you provide Rufus' log here so we can see what it says? Otherwise how can we guess? Also, did you first confirm with the SHA1 hash that your downloaded ISO is fine?
Yes of course: Found USB 3.0 device 'SanDisk SanDisk Ultra USB Device' (0781:5581) 1 device found Disk type: Removable, Sector Size: 512 bytes Cylinders: 1885, TracksPerCylinder: 255, SectorsPerTrack: 63 Partition type: MBR, NB Partitions: 1 Disk ID: 0xB6AB2347 Drive has a Zeroed Master Boot Record Partition 1: Type: NTFS (0x07) Size: 14.4 GB (15504899072 bytes) Start Sector: 1, Boot: No, Recognized: Yes Scanning image... ISO analysis: Image is an UDF image Disk image analysis: Image does not have an x86 Master Boot Record ISO label: 'CCSA_X64FRE_EL-GR_DV5' Size: 2031240 bytes
My guess is you got a typical dumb first level support guy who activated your system using a fresh key. Meanwhile I'm sure everyone including you having problems activating after a clean install (despite having a DE and no major hardware changes) will eventually have their systems auto-activate. Me too, which is why I said it fails on some older systems. Most likely a quirk of the BIOS.
Never used rufus to create boot media for Windows so cant comment only this stands out to me. Error for 32bit MBR when you using 64Bit image