New
#330
Thanks for the update and let's hope so. A new build would be nice.
update:
#windowsinsiders; we are not releasing a build today as we are testing the upgraded build monitoring system to make sure everything's a go.Tweet
— Twitter API (@user) View on Twitter
Sometimes when we report issues, quite a few responses are, "works for me". What they don't say, but infer, is that the problem is caused by the "nut between the chair and the keyboard". What I'm saying is that there are too many issues for this to hold true.With "works for me" said, I will say that there are far too many issues being brought up to discard them as being caused by the "nut between the chair and the keyboard".
I've had issues that no one would believe were happening. So, I'm saying that even tho I don't have this or that issue, they're still legitimate complaints.
@Berton
Your problem sounds very much like one I had last week; I upgraded a machine that was running the build just previous to the last one. I saw blank fields everywhere keyboard input was expected. I remembered how to change my password to the pin number I use (which blanks to enter) and my desktop came up with the 14915 watermark, but still every page I tried to enter data on came up with the right graphics, but blank fields where keyboard data expected. Moving the cursor around drew pretty pictures with blank fields looking for input. I tried my Macrium restore and got some nonsense about my account neede to be updated with the correct privileges, could not restore system. (i did mess up my data files with older stuff.) The one saving factor is most output displayed fine, I could read data, just not see my responses, although they were accepted as expected. Long story shortened: I was able to open Device Manager, select Display adapters, and driver properties. Roll back driver got a Microsoft Basic Display driver that accepted keyboard input and displayed it in the appropriate fields... Machine works again, just needed some basic adjustments to graphics, font sizes. HTH :)
I think this is a very important point. Over on the SevenForums, someone had a very heartfelt complaint about an issue he was having, and asking for help. Rather than help, he got a chorus of "it must just be your machine". When I pointed out that 'it works for me' is not help, I got scolded for being trollish! I said that I thought it was out of line to call me a troll. One of the mods replied 'out of line, eh?', and I was banned, PERMANENTLY, for RUDENESS. I was a member for 8 years, had lots of good rep, etc., and I was summarily canned. That mod should not be a moderator...
This is the problem I posted:
Solved Insider Preview 14915 broken - Windows 10 Forums
I've tried 3 times to go from .905 to .915 but ended up going back to .901, lost my .iso file for .905 and Windows Update will only give me .915, so far quite useless.