In the case of preview builds, it's your responsibility to find beta drivers to install, not Microsoft's. If it were the final build and they didn't have a working driver, that would be very different.
You need to find the drivers. Check with the mfg website, sometimes older drivers work, sometimes the latest, it can be a crap shoot at times with these not-ready-for-prime-time OSes.
more data mining. seriously, it's a good approach for MS, but do they think that corp's are going to want to do that. as far as retail customers go some will and some won't. i myself refuse to sign up for a Store account of MS account. next could come a marketing nightmare. if that is going to be their policy, on a retail copy it will have to be stated clearly on the box that you need a store account. or maybe they're going to go the D/L only route, with no store sales. it doesn't really matter because MS makes just about all there money on new computer sales, and far less on actual upgrades or full installs. g/l to them.
maybe the esd doesn't install the data mining, because it's an upgrade and uses the older files. yeah right we should be so lucky.
you think MS would think of something as simple as that. now the question that needs to be asked is what exactly is it doing behind the scene that kicks back an error from one of their own AV ( should we call it that ) programs.
No, the Operating System is not complete without a cliche launch that Microsoft must do. Also the features inside Windows 10 are dull and boring. Most of these features have been in Apple OSX and Linux for at least 10 years. I mean maybe the reason for adding them is to make it look like MS is no longer a dick to the people who don't have a Touch Screen computer.
damn that was a long post. just let me say that if i had that problem it would bug the hell out of me i would do the same thing and ask if anyone had a fix. the computer info would be helpful if it is a simple driver problem. as far as MS not spending time developing this or that because somebody is looking to fix such a problem is exactly what the Technical Preview is for. imho your post was uncalled for and made a new member feel that their problem was insignificant and not worthy of anyones time.
Actually I agree with Vali20 completely post wise. I really have no clue why Windows 10 is under the current development plan. Microsoft is not apple as it is trying to look stream lined. The current changes in the operating system are so minor they at most would not be recognized if you compared Windows 10 Alpha build 9860 to Windows 8.1 Update 1 build 9600. Yes I understand that your trying to draw attention to the fact that your fixing the abomination called Windows 8 however this is not the right way to do it. I note all the changes that are being incorporated into Windows 10 but testing it out in such a fashion is premature. At least give this operating system to the developers then show us a Beta and not a rushed out s**tty Alpha. That has not even been Feature locked let alone locked down for what the overall vision of the OS is. I have no idea what the end result of this rushing will be but this does not make the development environment any better.
just saw Tito's post 1 page back about merging threads. was wondering why there was so much for me to read after just 24 hours. now all i've got to do is D/L the new build. hopefully all the hoopla has died down and the servers aren't being over run.
windows 10 enterprise not activated after build update to 9860 what the title said people, got the key and tried to activate and got this: --------------------------- Windows Script Host --------------------------- Activating Windows(R), Enterprise edition (72e02447-a7bc-462c-9c3d-e5c919a5140a) ... Error: 0x80072F8F On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0x80072F8F' to display the error text. --------------------------- OK --------------------------- please help! thank you
Sorry to ask that, bu i didn't found the reg file in order to be able to update my Windows 10. Download is OK, but unable to install with the code 0x80070032. Anyone could help me please ? Thanks a lot
Did you make update or clean install ? because if build 9841 activated, not must be problem after updating to 9860.
@scandal1981 I have merged the thread. You can always try phone activation (& even if use existing KMS activators which isn't supported by Microsoft). Seems that activation servers can't be contacted from your place.
@tito thanks man I didn't know It goes here keep up the good work! to everyone else: phone activation worked great if anyone has same problem with activation apparently happens with updating builds not with fresh 9860 install
The upgrade process resets Windows RE and adds setosimage to point to the install.esd in that folder for System Refresh/Reset. It also can register the new winre.wim to C:\Recovery instead of upgrading the system RE tools partition (presumably due to a bug). Better to keep that folder, along with the $UPG$PBR.MARKER file in the root of the drive, see the textfile in the RecoveryImage folder. Though if you don't plan to use System Refresh/Reset, you can remove the RecoveryImage folder and the marker Redeploy WinRE. Mount the RE Tools partition in diskmgmt.msc, assign a letter (e.g. T: ), then copy C:\Recovery\winre.wim to another place to avoid it's deletion (during the reagentc /disable command ) then in elevated console use reagentc for redeployment Code: reagentc /info reagentc /disable md T:\Recovery\WindowsRE copy path\to\saved\winre.wim T:\Recovery\WindowsRE\winre.wim reagentc /setreimage /path T:\Recovery\WindowsRE /target C:\Windows reagentc /enable reagentc /info bcdedit /enum all Unmount the partition (remove the letter) and repeat the last command to verify. In {current} , recoverysequence must match the recovery section identifier , whose device shall point to the unmounted partition you saved winre.wim to, in the format of e.g. [\Device\HarddiskVolume1] P.S.: you can ignore the leftover recovery identifiers used by the previous system (not sure how to remove them, bcdedit /delete doesn't do it, and easybcd doesn't see recovery identifiers), and the Device options sections on the bottom
Because you don't have the right permissions to do so, you can get permissions by running the following command in an elevated command prompt: Code: takeown -f "C:\RecoveryImage\" -r (while you're at it, try the new command prompt features like copy/paste ) EDIT: Yeah, what Arseny92 said