New
#220
Hi,
O, don't worry about. I was the one making the initial mistake anyhow. I should have looked up the correct word in the first place.
Thanks for offering anyways.
Cheers,
Hi,
O, don't worry about. I was the one making the initial mistake anyhow. I should have looked up the correct word in the first place.
Thanks for offering anyways.
Cheers,
I never seem to lose the Workstation 12 Player at all while I previously saw the VM Player 7.1.2 out a month before the 10 launch date updated to the 7.1.3 while no longer found as a download at the VMware site itself. You might want to consider going for the WS 12 Player which might also mean seeing replacement VMs fired up as well however but not keep running into the replacement install necessary each time a new build comes along.
For the separate Creative sound card on the main the software portion for the audio panel and entertainment console with large volume control knob, speaker setting,s EAX, equalizer, etc. has to be repaired each time running the web update installer while the onboard on the second desktop(Realtek) never runs into any issues from build to build.
The one thing to note about this build is simply the one change seen for the Edge extensions and nothing else which suggests something was already pooched on the existing previous build's install that brought out these problems with the number change on build being the only other difference. Both desktops here as well as several VMs later and not one iota of a problem being seen other then that need to refresh the Creative software.
FWIW In 14291 had to re pin all the apps but 2 into the start menu to put them back after they vanished .
There are some Icon shortcuts I made or simply put in the start menu program folder earlier and pinned them to start normally that worked before and recently vanished from the start menu along with the other links and shortcuts some are still in the start menu program folder but not on the application list . .
Now they refuse to appear on the apps list or start menu where they were also .
I may try removing those from start menu program folder ,restarting and putting them back in the start menu program folder .
I will have to pin some shortcuts back into task bar that vanished also . The taskbar notification area is fine as is taskbar search and 14291 is more stable than 14279 but its using more ram even idling .
What was ironic was missing a few builds in December and January until the TH2 update got flaky! Now this is the general release upgraded from the 10586 Insider that needed replacing by the 14257! You would think the general release would be less problematic then a developer build? Apparently not the case yet for 10! For 7 in contrast going back to the last single platform offering the RC was almost the same as the RTM for how well those builds performed.
At the times 7 was in prerelease status you only saw the Ultimate edition beta builds for the public back then not seeing any Home Premium or Pro developer builds unless you had an MSDN or TechNet paid subscription. MS was pushing the Ultimate flavor apparently at the time. Now they simply want everybody((or as many as possible) running 10. The ei.cfg file was then removed from the 7 iso in order to see it unlocked for trying out the HP and Pro while with 10 you have the Home, Pro, and possibly Enterprise builds to examine.
With some builds turning out buggy following an upgrade over previous what lacks is no longer seeing each new build available is iso form but by way of the WU itself. Often the problems are not bugs in a new build but like this one only seeing the Edge extensions suggesting something in the previous build is off and being carried into this one. With the only real changes being with Edge a web browser how could it trash a working build unless something else is off?
I cannot select text in Word, nor can I select what's in an Excel cell. I can't double click on the "borders" between cells to enlarge or decrease to fit the content. IOW, double click will not work on anything. I even tried it on Notepad and it doesn't work there either. If I wanted to go back and select the second word in this post (cannot), I could not do it. Everything else mousewise works, though.
Having gone straight from the TH2 to 14257 immediately before the 14267 arrived and then onto each build up until now and not seeing any of these problems I have to suspect there's a common element I have been missing as to why so many others are having issues. The problem is trying to isolate why people are running into bugs since each has their own personal setups going.
I could see some having UEFI since the builds here lack that factor as well as running with AMD while others have Intel. But even the spinner vs SSD factor may or may not have any bearing on this. My best guess would be an UEFI element besides the various software environments as a potential hardware related if any type issue while the latter as far as software combinations would seem to fit the bill the most.
This would be the most likely since we are running developer not general release type builds. The TH2 going buggy did see some patches as you will note from the three digit extension change after the November 10586.73 seeing the latest 168 instead. Another person was seeing 162 apparently having missed something there.
A clean install now with the MC tool would be seeing the 168 or should anyways see that while I am still looking at the TH2 from the Tech Bench page to see if that number matches. A new VM will likely be needed but over on the second test case. Once on however you simply wait for the next build if needed to see that upgrade over the TH2. I would suggest taking the updated form of TH2 and seeing the "Windows.iso" download of that turned into the media used for the clean install and wait a bit to see if the updates that is supposed to have seen are working before grabbing this or the next build as the update.
First see if the bugs there were corrected or not. If you find it works out make an image first before enabling the Get insider builds option to keep as your backup file. If you then run into the same problems with this build or the next you can simply roll it back.