The latest update on Aug. 17 has solved this problem. I have checked and double checked on many time zones, the bug is not there anymore. Thankfully MS guys finally saw the bug I guess.
Type: Posts; User: emeshnep
The latest update on Aug. 17 has solved this problem. I have checked and double checked on many time zones, the bug is not there anymore. Thankfully MS guys finally saw the bug I guess.
As I have mentioned I am an insider so I got the copy of build 10130 from Microsoft insider site. After that, all the other builds up to latest and final 10240 is updated directly from windows...
Anyone else in the same league?
Until microsoft comes up with right fix, restart and then disable cortana. If it still keeps doing that, try with different windows ID if you have any other. Good luck
My issue is kind of strange. I am an insider currently on Windows 10 build 10240. All the build I have tried so far has this same error in task scheduler when I change my time zone to my current...