New Windows 10 Insider Preview Fast + Skip Build 18329 (19H1) - Feb. 1 Insider

Indexing is running extremely slow.
I have rebuilt the database to no avail
Anyone have any fix/workaround?
Searching is nigh-on unusable right now due to incomplete indexing

Hi folks
The VMWARE problem is a deal breaker for me on this OS -- I can live with various defects on these insider builds - they are pre-release etc so one should expect odd glitches -- however I use a lot of Virtual Machines so Virtualisation has to work properly before I'd even think of using these builds seriously. HYPER-V IMO for some older legacy hardware isn't really yet for prime time (Sorry Kari !!) although I'm sure that will improve -- .

What I find frustrating in these builds is that sometimes when a problem is fixed in one build it re-appears again in a later build -- I just don't believe today's developers understand what is meant by regression testing --- not very exciting I know but it's an important part of the process before releasing stuff as production quality.

So I'm parking this build and wait for the next one -- fortunately it's only around 10 mins to image it and around another 10 mins to restore earlier build.

E.g IE 11 menu woes (I still need IE11 for accessing corporate software though (SAPGUI stuff etc).

Ist session menu is fine but if you open another session then no menu and menu on ist session is grayed out !!!! how in the world did they do that !!. The ist session menu is OK when you make that the focus though -- weird !!!!





Cheers
jimbo

jimbo45 said:

Hi folks
What I find frustrating in these builds is that sometimes when a problem is fixed in one build it re-appears again in a later build -- I just don't believe today's developers understand what is meant by regression testing --- not very exciting I know but it's an important part of the process before releasing stuff as production quality.
jimbo

In my previous experience as a tester I would suggest this is also down to poor config management

Hi there
@kado897
It's really not necessary to have weekly releases - at least for external (i.e non Microsoft people) users -- I'm sure switching to say every 3 weeks for insider builds might supply a bit more robust consitency. I'm sure also managing several different releases at the same time with limited staff numbers isn't also a good way to getting the best product quality out of the door -- some of the management has to be blamed here as there are only so many hours in a week that these testers can work.

So far I'm fairly unimpressed -- if you look at rolling releases of say OPENSUSE, UBUNTU, CENTOS etc these all seem much more stable -- Linux updates used to be a mega lottery now they all seem to take place quite smoothly with far less problems -- perhaps Windows should look at that model for updates and make more use of open source developers who really can fix a lot of errors quickly -- a valuable often free resource too.


Cheers
jimbo

Hi folks

another regression found on this build.

VMWare Workstation -- XP and W7 VM's won't run from external USB drive - Host is W10 pro X-64 latest skip ahead build. Linux VM will run but won't attach any USB devices -- even when VM indicates connected.

just get black screen and VM never boots up -- can't shut VM's down either.

Same XP VM from same external HDD running on current (normal) Windows build. External devices can be attached too without problem.



seems something with USB devices on this skip ahead build. Will now wait for the next one.

Cheers
jimbo

f14tomcat said:

3 weeks? Nah! That would move the Insiders up to the Nose-Bleed seats. If a build croaks on ya, just skip it. Besides, frequent builds are good for moral.

A little aggravation can be so relaxing. :)