Regedit32
Moderator
- Joined
- Mar 4, 2016
- Messages
- 3,609
- Reaction score
- 1,141
After an initial failure at the 75% mark to successfully upgrade, followed by a successful upgrade on second attempt I've run into a few apparent issues:
That is it from me for now. Will keep updating this thread as I discover other anomalies.
Please feel free to share your own discoveries, but please keep it to the error/bug you found, and any steps you took to overcome / fail to overcome it so far. I do not want to see I hate Microsoft posts, which are not constructive.
If you see a post here from me or someone else showing their discoveries that you too have been through in the current 16125 rs_prerelease and managed to resolve, please share your tips.
- Microsoft Edge has become somewhat less stable
- It appears to lag/freeze often and gives the appearance that it has lost focus when you attempt to type in address bar. When this happens on occasion a notification will appear informing you C:\Windows\Explorer.exe has run into problems.
- Resolving the immediate issue requires restarting Windows Explorer, but to get to the Task Manager to do this either by right-clicking the Taskbar or using the Ctrl|Shift|Esc shortcut seems to fail on first attempt to open the Task Manager then work fine on the next attempt. Restarting Windows Explorer helps but does not have a lasting effect. The issue appears to be intermittent.
- It appears to lag/freeze often and gives the appearance that it has lost focus when you attempt to type in address bar. When this happens on occasion a notification will appear informing you C:\Windows\Explorer.exe has run into problems.
- Right-click and/or Winkey combinations to achieve same goal (for example winkey|x) will work, but often only on second attempt. The first attempt will see Power Menu, or a Context Menu for example pop-up, but before you can select your choice from the menu it disappears. On the second attempt it is fine and works as you want it to.
- Device Manager appears to run into trouble randomly if you attempt to update/roll back drivers. This behaviour though is rather random, as often it works perfectly fine.
- In my test I updated all Intel chipset drivers to 2nd generation, and eventually succeeded. In normal mode, when error occurs, the Update dialog enters an infinite loop showing progress bar, or after a few minutes displays a timeout error message.
- When done in Safe Mode (no network support) the updates all appear to work fine [ no loops/timeout errors ], however some of the confirmed updates do not stick after restarting computer.
- Safe Mode (no network support) pops up two errors consistently:
- As soon as you sign-in to Safe mode you are greeted by a large Tips app that crashes almost instantly. Overlaying this app, you are greeted by a smaller pop-up informing you CTFMON.exe is not working.
- You click OK to the second error, and the X to close Tips app to get to your Safe mode desktop.
- Now every time you right-click or press Enter or click buttons in applications such as Device Manager the CTFMON.exe pop-up reappears and you have to click OK to continue
- Ralink 802.11n Wireless Lan Card displays in Device Manager with the yellow warning triangle.
- Windows cannot initialize the device driver for this hardware. (Code 37)
- Attempts to update drivers, or use current drivers on computer, or install new ones using downloaded Setup all fail to work, both in Normal and Safe Mode.
- Disabling and re-enabling has no affect in helping
- Network Adapter troubleshoot app does not find any issues
- One driver update resulted in not only continued loss of Wireless, but then Ethernet also crashed!
- Thankfully, Network Reset via Start > Settings > Network & Internet > Status worked to restore Ethernet. It had no positive affect on WLAN, but did manage to report Drivers need to be installed.
That is it from me for now. Will keep updating this thread as I discover other anomalies.
Please feel free to share your own discoveries, but please keep it to the error/bug you found, and any steps you took to overcome / fail to overcome it so far. I do not want to see I hate Microsoft posts, which are not constructive.
If you see a post here from me or someone else showing their discoveries that you too have been through in the current 16125 rs_prerelease and managed to resolve, please share your tips.