New
#41
Everything going fine except the sfc /scannow was broken after first few hours of play. After run the dism repair, it came back well. Smooth and fast. Nice build.
Everything going fine except the sfc /scannow was broken after first few hours of play. After run the dism repair, it came back well. Smooth and fast. Nice build.
After the many problems in 547 it is nice to have all the good stuff happening, and all the bad gone. The one thing that got my goat with 547 was the fact that on my "D" Drive I had all my music; when updating to 547 it all just disappeared (GRRRRRRRRRRRR!). Thank goodness for backups. . .not sure what caused it to just go into cyber space, albeit it didn't happen with 565 (knocking on wood). . .
Hello again,
Can anyone please try to search for an inexistent, arbitrary, registry value and post what is happening? In my system the Registry Editor keeps searching for ever, and then when I cancel it, it restarts the editor. It behaves like it's crashing. I describe this issue in my post #2, in this thread.
Clean-installed build 10565. DISM and sfc /scannow report no issues. No tweaking, no modifications on this build. Only two applications installed: CCleaner and HWiNFO64. I've never cleaned the Registry.
On my main OS, build 10240, Registry Search works fine.
Thank you.
The only problem I have is the same one I had with the last build. When I open EDGE it takes 25 - 30 seconds to populate and connect to internet. IE 11opens and connects instantly. I would just use IE but Edge is initially set up to open PDF files and it is the same problem there with the excessive lag time. Have to go back after each update and point PDF files to open with Reader. If MS wants to migrate users from IE to Edge they have a long way to go. I have 2 PC's running different versions of Win 10 and same problem on both.
All fixed now for some reason unbeknownst to me. I searched the Net last night and found a tute on how to uninstall and reinstall Edge, which didn't work to reinstall for I think the script for the Command Prompt was not meant for 10565. I new it was risky, but thought I could always perform a Restore of which I made a point after upgrade. For some reason that fixed my link issues and all is fine. Go figure!