I do get an intermittent unable to connect to activation servers in settings and connect to internet tp activate in system (control panel). This is on 1709 and after putting genuine ticket in C; correct folder. This to to deal with watermark of activation. Any solutions. Troubleshooting does not work and this is a problem. Keys are genuine win 7 key used for 1607 initial activation. This is only a problem in 1703 and 1709.
If you already have established a HWID/Digital License, you don't have to use the genuineticket again, the Digital License is valid for the lifetime of the hardware (mobo in most scenario's). At installing don't insert any keys and the HWID will activate the install by itself.
I get it. Last month, I bought a new system with cpu, mobo. So I installed 1607 and during install screen, inserted my win 7 genuine key. It activated and so did 1703 or 1709 when I did a clean install sometime later. The problem is this intermittent messages in 1703 and 1709. First the watermark appears. Then I put in a genuine ticket, restart. The watermark disappears and is replaced with `unable to connect to activation servers' or `connect to internet to activate windows'. At this stage, when I see the genuine ticket location, genuineticket.xml has disappeared. So it has picked up the ticket and so the watermark goes but the above messages remain.
You could simply try the key again, if the message "can't reach the activation servers" you probably have done something wrong, disconnect LAN (just to be sure), reboot, insert ticket, reboot and after this last reboot connect lan again.
Indeed, create a shortcut to shutdown the computer, a script (bat) to close all known programs and then shutdown, like: Code: taskkill /f /im iexplorer.exe taskkill /f /im chrome.exe taskkill /f /im whatever.exe shutdown /s /t 00
Anyone else having issues with the photos app? Mine seems to like to refresh itself far too often and due to me having over 20k pics it can run up to an hour a time, it wouldn't be so bad but the things eating up 30% CPU causing the laptop fans to kick in above idle. If I look in the task manager it shows runtime broker nested under photo's I google the hell out of this and got nothing back that really helps. Any ideas? Thanks.
I did a clean install (on Test Rig 1) from a .iso DL from WZOR/MS & a MDL link. I wiped the existing W10 x86 OS I had installed & installed this (build 16299.15 x86), it was my fasted yet install on a 7200 RPM HDD. After getting my setting choices how I like them I started installing apps. After a few x86 apps I installed a 16bit app, had to jump through some hoops but was successful & it runs quite well as do the others I installed. Think I'll keep this one.
Are there differences in features between MSDN editions and those created with esd files of Windows 10 v1709? If not, what are their differences? Thanks Bye
There is no difference in content between the two. The only thing is that the isos of MSDN/VLSC are a little more in size and the isos generated by esd files change the hash every time they are created.
For me the problem happens in windows 10 enterprise but not in windows 10 pro. Updating the UEFI firmware as Psyort suggested does not help