I'm having a nasty fonts problem since upgrading to this version of windows. I've tried programs such as maintype or fontexpert to install fonts, but randomly after a few reboots (either restarts, or shutdown->on with fast boot) fonts appear as installed but programs (word, PShop) can't access them and error out. Under fontexpert only reinstalling the whole program + fonts and deleting databases solves it, and with maintype it's (only) needed to uninstall and install again such managed fonts (without any reboot in the middle). sfc /scannow finds no problems. I still have to check if for some reason it's AV related, and to confirm if it happens on another PC/installation. Edit1: Just noticed that a new maintype version was released today, forcing fonts installation to the windows folder. I'll check it later and update this post with any findings, as both programs weren't doing it (maintype would load directly from my own lib, and fontexpert would copy to it's own lib at appdata\roaming). Edit2: Maintype 7.0 b1032 seems to have fixed it, so it looks to be a problem with (some?) font managers that don't directly use the windows fonts folder under RS2.
Has anyone had any activation issues with 15063? I am having some activation issues that are strange. If doing an in-place upgrade of a windows 10 install in a system that already had a digital license, it will activate fine. If doing a clean install in a system that already had a digital license, it will activate fine. However, if deploying from an image to a system that already had a digital license, it will NOT activate fine. Base windows install created and tweaked in a system that already had a digital license where it activated fine. Image is created from this install. Then, deploying said image to a different system that already had a digital license, it will not activate in the new system The hardware is identical, so the image deployment is the faster route of configuration. When trying to run the activation troubleshooter in the new PC, I get the message "A digital license for windows 10 home has been found for this system running windows 10 home. Install windows 10 home to activate" No sysprep applied to the windows install before creating the image, and the image is being created using Norton Ghost 11.5 I have done it this way a lot of times in previous win10 builds (1511 and 1607) and it took a reboot at most for an image deployed in a new system to pick the activation. Thoughts?
Did anyone grab the "official" Windows 10 Creators Update ISO EN-GB? The one labelled "Windows10_InsiderPreview_Client_x64_en-gb_15063.iso"? I would like to get my hands on that one!
Good job I say, but let's here from abbodi1406, remember what they pointed to in their post. Thanks anyway.
Blue light option is almost unusable, anyone get it to work? my blu elite has been working fine, and still today on 15063. no issue and real time. is the only way I test.