Here is a new spotlight image I haven't seen before that appeared this AM. Has anyone else seen this one before, if so what build?
I would had thought by now that Microsoft would had fixed it Mail app. In all builds what up to current Insider build. Still get a error message "Your gmail & yahoo settings are out of date"
Added to the OP: ALL UUP Files available at @mkuba50's UUP DUMP [Online/Offline] https://forums.mydigitallife.net/threads/uup-dump.75052/
Look into HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion and you'll see BOTH names: short one as a value of EditionID, ProfessionalWorkstation and long one as a value of ProductName. For me short one is more convenient and CORRECT.
Sadly it's not. With introducing license switching they created a mess when retrieving the values from registry, so i started using WMIC for accurate info.
What for that OLD and UNSUPPORTED tool is necessary at all: PShell command get-item HKLM:\"Software\Microsoft\Windows NT\CurrentVersion" outputs: Name Property ---- -------- CurrentVersion SystemRoot : C:\WINDOWS BuildBranch : rs3_release BuildGUID : ffffffff-ffff-ffff-ffff-ffffffffffff BuildLab : 16281.rs3_release.170829-1438 BuildLabEx : 16281.1000.amd64fre.rs3_release.170829-1438 CompositionEditionID : Professional CurrentBuild : 16281 CurrentBuildNumber : 16281 CurrentMajorVersionNumber : 10 CurrentMinorVersionNumber : 0 CurrentType : Multiprocessor Free CurrentVersion : 6.3 EditionID : ProfessionalWorkstation InstallationType : Client InstallDate : 1504338502 ProductName : Windows 10 Pro for Workstations Insider Preview ReleaseId : 1703 SoftwareType : System UBR : 1000 PathName : C:\WINDOWS RegisteredOrganization : RegisteredOwner : [email protected] ProductId : 00395-40000-00002-AA018 DigitalProductId : {164, 0, 0, 0...} DigitalProductId4 : {248, 4, 0, 0...} InstallTime : 131488121025556669 EditionSubstring : produced by Contoso
Not sure what you mean by old and unsupported. As said, the reg entries might be correct for this version. BUT take a Pro and license switch it to ProEdu by entering the ProEdu default Retail key and check the mess in the registry .
Well, I haven't played with EDU but I've seen no problems when switching SOME times Pro <--> ProWorkstation. Really I hate WMI at all and always prefer to use DIRECT SOURCE of the system data which is Registry. Though there are some cases when my knowledge is not enough to convert Registry data into readable format, e. g. haven't yet found a way to get activation key from UEFI BIOS data in Registry and HAD to use WMI request to get this data. P.S: I also use additional sources like setupact.log, SoftwareDistribution\ReportingEvents.log which provides additional data and timestamps for the installation actions and sources.
Doesn't work for me but thanks you AllowAutoGame wasnt there but i put D-Word with 1 in it , restarted,, still not showing up. I appreciate it though.
Okay. Don't expect to see the Game Mode displayed at the 'Settings' in this Build. For you to be sure your Game Mode is on do this: 1. Push the "Record game clips, screenshots, and broadcast using Game Bar" toggle to on at Settings. 2. Run your game. Now press the Windows Key + G to open Game Bar. 3. Click on Settings icon and check the box beside "Use Game Mode for this game". NB: That will only affect individual game despite putting on Game Mode using Registry Editor previously.