Found dependence when the conductor starts to hang when working with MKV files. If the file conversion was done by a 32 bit program, then there will be problems with this file on a 64 bit system. And if you converted a 64 bit program, then there are no problems. Check who can.
The same problem here. I have to reboot into safe mode to make any changes to MKV files. Any other workaround found? Also, it seems there are some problems with Recyle Bin. When files are deleted, it doesn't show Bin contains any files. I have to open the Bin to see the files and manually remove them.
h'mm my cursor is sticking monumentally and at times sometimes disappears off the page, I've never had this problem before......haven't installed any new programs so a puzzle for me OR does this build have a bug.
D'oh I'm using an optical mouse and seems a bit of dirt has stuck on the pad where the mouse is traveling over...so cleaned it and so far everything seems ok and looks like a false alarm.
if it is a wireless mouse that type if thing will happen too when the battery starts to die or the connection is bad.
Today I checked my suspicions all day and they were confirmed. Everything is exactly as I described above. The problem with 32 bit applications for encoding MKV files on a 64 bit system.
I'm not having any issues with MKV files here, regardless of the size or the version of mkvmerge that was used to mux the file, but AFAIK I have Icaros Property Handler installed as part of K-Lite Mega Codec Pack, so it might be related. On other news, though, I never got Windows Sandbox working. It has been a while since it got introduced and we're already moving to the final stages before 19H2 19H1 gets released to the public so I though it would be better to ask. When Sandbox was introduced, it just silently closed whenever I tried to start it, on the last two builds I actually get a generic error message saying it couldn't be started and asking me to go into a specific category in Event Viewer for more details, but all I have in that category is an info log saying the VM was asked to start, then nothing more, so I'm clueless. If that helps, I also have Hyper-V enabled and can run Virtual Machines through it just fine, however Windows Sandbox simply doesn't launch here no matter what...
All I'm saying is, look at how many times a scheduled release has been delayed in the past. Nobody knows for sure what month 19H1 will have a bug-fixed final release. With almost every new insider release lately new little things are broken. They're working on fixing bugs, while they're also working on new features that introduce new bugs. It's as if nobody at Microsoft has full control over the entire operating system anymore. Team A works on a new feature which introduces a new bug, which Team B has to fix, while Team C changes something that Team B didn't anticipate, so then Team B fixes what Team C changed while Team A tries to integrate what Team B did to fix everything, which introduces a new problem because Team B didn't anticipate what Team A just did. Throw into the mix hundreds of thousands, or more, insider bug reports that have to be prioritized, which cause new changes, which no Team anticipated. Windows 10 keeps morphing too fast for Microsoft to adequately keep up anymore. Any operating system is incredibly complex. Especially Windows 10 that keeps changing all the time. I thought with 1809's 17763.1 file deletion fiasco that they'd slow down and work on bug fixes, but they're too busy introducing new features to concentrate on that. So even when 19H1 is released, we don't know what bugs will need to be fixed with a new update which introduces new bugs that have to be fixed by another update that introduces new bugs. 1803 was delayed about a month. It was scheduled for release on April 10, 2018, but wasn't released for general availability until May 8. 1809 was delayed about 2 months. It was scheduled for release in September 2018, but released on October 2, 2018 which was then pulled on October 6 and re-released on November 13. So if the pattern continues at the same pace, 19H1 will be delayed 3 months. That's why I said that 19H1 will be released in March or April or May or June. And I'm not even sure of that.
of course it could be delayed or even blocked for some configurations of software/hardware if there are really critical bugs, but that delay or block is only for general public and only through Windows Update, not for insiders.