[Bug] FeatureScanner will not create txt file after finish (exception error)

[Trackah123]

Describe the bug
After FeatureScanner is completely finished, the txt file is not saved or generated, therefore i cannot use optional features like "Save the Features.txt File"

To Reproduce
Run FeatureScanner -> Introduction and setup -> download debug symbols -> scan debug symbols for feature ids -> done (error)

Expected behavior
in my case "22631.txt" should have been generated or saved properly.

Desktop

• Windows Build: Windows 11 Pro 23H2 (x64) (22631.3737)
• ViVeTool-GUI Version: v1.7 PRE-RELEASE 2

[MNLierman]

Looks like I'm having the same issue. I don't seem to receive any error messages and nothing appears to be logged in Event Viewer either, the result is the same, no features list is saved. It's hard to tell what the issue is or how to generate a list. I'm trying the old version now. I have a feeling that all of these tools were abandoned. This one hasn't received updates in 2 years. Rafel left all these projects because he said that no one in the community wanted to help contribute and it was always a race for who was first to post about new features.

I do agree that Bing and Google are flooded with low effort AI generated regurgitated trash blogs. Many of the site owners generated vivetool related stories for the clicks and ad revenue. You Google or Bing any error and the advice is DISM DISM DSIM, SFC SFC SFC, good god STFU. Not every error means you have corrupted Windows files. I actually can't think of very many times that SFC and DISM actually corrected a Windows issue. Mainly those were instances where we found out an HDD was on it's way out.

[PeterStrick]

@MNLierman To be honest, ViVeTool GUI hasn't received any Updates except for the v1.7-Testing branch due to me having lost motivation in developing it further as I am no longer using Windows myself and switched to Arch Linux

It hurts me though that I lost motivation in this project as it gained a lot of traction, even landing in a Top 10 Starred VB.Net GitHub Repositories list

I guess most v1.7 Code theoretically is done, it's just really testing it that's left, which has become a bit annoying as GitHub has removed the old v1 Projects Kanban board which I used to keep track if what I tested and didn't test yet

[MNLierman]

Update: I did some testing and the feature scanner from 1.6.2 works but the one in 1.7 doesn't.

I guess most v1.7 Code theoretically is done, it's just really testing it that's left, which has become a bit annoying as GitHub has removed the old v1 Projects Kanban board which I used to keep track if what I tested and didn't test yet

I'm not sure which version of Projects you are referring as I haven't seen the Projects change drastically, it still is a great resource for my other repos, and I see bigger projects organizing app goals/timeline, bugs, features, releases, and user requests into large boards. I didn't start using it until mid-2023 so perhaps you're referring to before then? In that case, I can understand, especially if it was a big change.

I guess most v1.7 Code theoretically is done, it's just really testing it that's left, which has become a bit annoying as GitHub has removed the old v1 Projects Kanban board which I used to keep track if what I tested and didn't test yet

I can help, and I also know VB.net and C#.

I was actually thinking how cool it would be if I could help bring the project to WinUI3 UX without the Windows Store. A lot of people think that to use WinUI3 you have to use the msix packages, etc., and that's actually not a requirement. It sure would be nice tho if the .Net folks decided to incorporate these runtimes into Windows 11 instead of requiring separate downloads or bundling it with apps. They claimed here on GitHub that not including these frameworks and runtimes with Windows increases adoption and prevents fragmentation. That's nonsense. It creates more fragmentation because if developers bundle the runtimes with their apps, they are responsible for releasing updates with new runtimes. Apps that don't receive frequent updates aren't patched with security updates and they quickly become fragmented. The best option right now is to force users to install .Net or the runtimes, and include an online installer stub with the app to make that process easier.

Anyways, don't get me started on Microsoft. I'm quite frustrated with them for a number of reasons. I'm sure that's why you moved to Arch Linux! It sure is nice to have an OS you do not have to worry about. Linux is pretty reliable as long as you don't have to worry about drivers or kernels; but I remember as a kid 20+ years ago, once I compiled the kernel to work with my hardware, I rarely had issues after that. Things just worked.

For Vive and feature flags, do you know a lot about them? I'm not well experienced with Microsoft's feature flag system and it seems to me that it's very hard to tell what's new, what's old, and what's dangerous to enable. There was a machine I had that I enabled about 50+ "sounds neat" things. Well those 50 things that "sounded neat" like "servicing performance fixes" etc, actually opened up old code pathways and things started crashing everywhere. It brought back old bugs and issues that I remember the engineers fixing in older Insider builds.

This brings to me a couple of feature requests, which shouldn't be very hard to do, and I can help the best I can: I created a new issue here with my suggestions.

[PeterStrick]

I was actually thinking how cool it would be if I could help bring the project to WinUI3 UX without the Windows Store.

Migrating to C# and a new more open source UI Toolkit like WinUI3 / Avalonia was actually planned for Version 2.0

I didn't start using it until mid-2023 so perhaps you're referring to before then? In that case, I can understand, especially if it was a big change.

It was the v1 Github Projects which were per-Repository instead of the v2 Projects which are now per-Account

For Vive and feature flags, do you know a lot about them?

No one except Microsoft knows alot if them, all we can do is try them out and see what happens. If something interesting happens then report our findings back

what's old, and what's dangerous to enable

v1.7 has a Feature Comments System that allows you to comment eg your findings on a Feature Flag that will directly show up in the UI

This brings to me a couple of feature requests, which shouldn't be very hard to do, and I can help the best I can: I created a new issue here with my suggestions.

Yeah it's best to discuss those there

[PeterStrick]

Update: I did some testing and the feature scanner from 1.6.2 works but the one in 1.7 doesn't.

Did you test the one from the v1.7-Testing branch or the publicly available v1.7 Pre-Release?