Author |
Message |
Registered: October 1, 2007 | Posts: 3 |
| Posted: | | | | Tahoma is installed in my instance. It hasn't been removed by the latest insider update. |
|
Registered: March 16, 2007 | Posts: 10 |
| Posted: | | | | I have the same issue and the same lack of success. I verified that the Tahoma font is installed and functions normally. I can't revert as 17025 has a fix to the previous version that I need for work so I'll pause using DVDP until the issue gets resolved. |
|
Registered: June 7, 2007 | Posts: 16 |
| |
Registered: July 28, 2007 | Posts: 1 |
| Posted: | | | | Ok Invelos, its time to fix this. Reverting Operating Systems is not fixing the issue, therefore not a valid suggestion. You have the logs and information. We need this fixed. |
|
Registered: March 18, 2007 | Reputation: | Posts: 1,636 |
| Posted: | | | | Quoting ken.barrett: Quote: Ok Invelos, its time to fix this. Reverting Operating Systems is not fixing the issue, therefore not a valid suggestion. You have the logs and information. We need this fixed. Unfortunately, I don't see Invelos expending any effort to fix this at the moment given this is a Windows preview build and not an official release build. It's quite likely MS broke something and it will be fixed in a future release. The same could be said for the DVDProfiler beta releases... |
|
Registered: January 27, 2009 | Posts: 181 |
| Posted: | | | | Works fine on very latest 1709 release build. Insider preview builds are just that, and no support from M$ for apps not working. They will tell you to go to the application provider. I would not totally blame Invelos if you are using a Beta build. |
|
Registered: October 1, 2007 | Posts: 3 |
| Posted: | | | | Agreed that occasional software breakages are the cost for running the insider builds, and all of us who run them should have gone in with that understanding.
However, the Insider Previews are just that, a window into the future of Windows, so I personally think that it would be in Invelos's best interest to at least investigate and determine the cause of the fault.
It may be that Microsoft have simply broken something and they will fix it.
It may be that Invelos are doing something odd, or non-standard, or is using deprecated Windows features, and that has thrown things off kilter. In this case, it is worthwhile making a call to see if Invelos want to align their product to the latest Windows technologies, or if Microsoft should be informed that they have broken some/an app(s) by making some arcane technical change, so they can restore the required features.
Either way, it'd be nice to know what the answer is. I am happy to wait and see for now, and can use the mobile app for logging disks in the meantime. | | | Last edited: by MisterQuade |
|
Registered: January 27, 2009 | Posts: 181 |
| Posted: | | | | Quoting MisterQuade: Quote: Microsoft should be informed that they have broken some/an app(s) by making some arcane technical change, so they can restore the required features. We run Enterprise version at work with Primier support from M$. When they came in to talk about the new servicing model, all they said was if an Application broke, then it was up to the application developer to fix their program. M$ had no interest in changing their code to suit. |
|
Registered: June 7, 2007 | Posts: 16 |
| Posted: | | | | Quoting specise_8472: Quote:
We run Enterprise version at work with Primier support from M$. When they came in to talk about the new servicing model, all they said was if an Application broke, then it was up to the application developer to fix their program. M$ had no interest in changing their code to suit. which is correct if it is a customized app. Imagine you would fix something in a million time rolled out product for one specific customer. Product bugs are a different thing, this where support is coming in. |
|
Registered: March 20, 2007 | Posts: 2 |
| Posted: | | | | Hey, so I had a thought that if the problem is caused by MS and this insider build maybe what we should do is submit feedback through the feedback hub app. Maybe if they see all of us do it then maybe it will become a higher priority for them to look into. Otherwise, we'll probably be SOL until the next Spring update unless one of the newer builds just happens to fix the problem before then. |
|
Registered: March 22, 2007 | Posts: 9 |
| Posted: | | | | Same issues with Build 17035. Interestingly, on my Insider Preview test machine I also have a trial version of a competitor's DVD cataloguing software installed that I play around with occasionally (just to remind myself why DVD Profiler really is the only option) and a very similar thing happens when editing a profile or exiting the program.
Has there been any response/acknowledgement from Invelos of what the issue might be? | | | Last edited: by MattH |
|
Registered: March 14, 2007 | Reputation: | Posts: 6,744 |
| Posted: | | | | Quoting MattH: Quote: Has there been any response/acknowledgement from Invelos | | | Karsten DVD Collectors Online
|
|
Registered: April 14, 2007 | Posts: 4 |
| Posted: | | | | I have precisely the same problem, and I know that it is a risk that I take when running beta versions, But reporting them is not the same as complaining,.if no one reports beta errors then what is the point of having beta testers? I have also reported it to Microsoft via insider hub |
|
Registered: March 13, 2007 | Reputation: | Posts: 3,197 |
| Posted: | | | | Dito.
I'm on the slow ring so it's usually not a problem but this time something broke. | | | First registered: February 15, 2002 | | | Last edited: by Nexus the Sixth |
|
Registered: December 1, 2010 | Posts: 4 |
| Posted: | | | | New build since yesterday (17035 ); same result. |
|
Registered: March 14, 2007 | Reputation: | Posts: 6,744 |
| Posted: | | | | My Windows was updated today to the official Fall Creators Update as Microsoft calls it. Version 10.0.16299.64.
DVDP 4 runs just fine. | | | Karsten DVD Collectors Online
|
|