New
#130
I would be interested in a presentation from the developers working in the dev channel but don't expect to see that anytime soon if ever.
Windows 10 Insider Preview Build 20175.1000 (rs_prerelease) - July 22 Insider
-
-
New #131
Hi there
seems to be these main issues with the last few "Beta builds"
1) Networking fails for a lot of people when trying to communicate TO some NAS devices (Non Windows) FROM Windows machines. - Whether this is due to "enhanced security" of networking or "deprecation of SMB1" whose to say -- but HOME users don't need Enterprise network security levels on a HOME LAN when just wanting to access data from NAS servers for streaming, file access or sending data to the Nas for backup. A lot of these devices are still quite old and still rely on SMB1 so it's no good suddenly dropping support or making connections almost impossible to achieve.
2) A load have reported issues with AMD processors not installing the releases either via WU or using UUPDUMP.
3) Even after a download and failed install the entire thing tries again to download and re-install - again fails -- surely the download should only happen again if there's a fix added to the original download.
Beta or not -- surely it shouldn't be impossible for the developers to test these scenarios before releasing the build -- and certainly what are the project managers doing who release builds without ensuring base functionality at least works.
These days who would even think of using an OS if networking was - to say the least - dodgy and unpredictable --should be a core component of the OS.
Of course as beta builds we expect things to possibly fail and come up with defects - but core functionality should always work --otherwise what's the whole point of it.
Back in the days where I used to work on some large scale projects - we probably would have been fired if we had let products out of the door without detailed and robust testing !!!!!!!
Cheers
jimbo
-
New #132
Jimbo. These are not Beta builds, they are Development builds so they are going to be flakey.
-
New #133
Well looks like you joined about a year before me so you may remember I was complaining for MONTHS that they were releasing builds that would not time sync with internet time servers. Finally fixed it - without comment. Don't expect any comments about the AMD problems (although I did post a screen print of a blue screen which probably somebody in virtual Redmond must have seen. I don't follow the forums but I don't think they release builds of Windows Server that are this shoddy. IMHO they should open-source at least some of the code so more people could try to patch it.
-
New #134
If you want to try the (hidden) new disk management menus, install and run vivetool
Code:vivetool.exe addconfig 23257398 2
-
New #135
Hi there
OK that's a "Technical distinction" really -- what I was trying to say that these builds do come with an "As IS" quality and people should expect odd defects and some unpredictable behaviour to happen on these builds --that doesn't excuse managers etc from releasing products where base functionality fails.
Imagine if Windows were released - but all video fails !!
These updates also shouldn't keep trying to re-download the whole wretched kybosh over and over again --these are quite time wasting even with fast internet -- when there's a fail --surely the last status should be kept in a log and before downloading the whole thing again the log should be perused to see if there's a problem and stop if the problem still exists. Every sensible database system on the planet has some sort of "recovery" logs available.
It's not difficult for project managers to mark out a few critical steps in a test plan, write a few test scripts for expected behaviour and then release when passed
Perhaps these people don't realize it but Ms still has one of the best bits of planning software on the planet --although a lot use EXCEL for planning - the PROJECT PRO part of the office suite really is first class -- anybody whose ever used it would probably agree -- all sorts of great things in it including resource planning, allocation, critical path etc etc.
It's a shame some managers over there at Ms don't seem to use it !!!!
Cheers
jimbo
-
New #136
I have not experienced any of the problems that Jimbo has.
Release notes state that there are problems with AMD installations....so one is prewarned.
Expecting non Window devices to connect on a DEV version is asking a lot, and we have been warned about problems
I could understand these complaints if the safer BETA version was installed.
-
New #137
-
New #138
I don't have a NAS and have not experienced a problem with an AMD (with the exception of a Blue Screen which I posted - the installation continued normally after M$ got their info and interestingly never recurred.) I completely trust @jimbo45's take on things 99% of the time - nobody - not even me - is right 100%. Blunder's like malformed warnings about AMD - from what we used to call Wintel no less - should not be happening on ALPHA's. Nobody testing with AMD could install this build or just continued after small glitches like a blue screen? Unlikely IMHO.
-
New #139
Unfair to say no problems with SMB1 when MS are strongly advising to disable it for security reasons. I have disabled SMB1 now and have to rely on mapping the NAS.
Quote
Related Discussions
