Recommended Posts

I understand what hes saying. Before I couldn't send feedback, it was asking me for a key. Then a few days after Windows was asking me to activate (don't think this means anything, just saying).

I check back today and I see that I can send feedback, same as in the picture in first post.

I understand what hes saying. Before I couldn't send feedback, it was asking me for a key. Then a few days after Windows was asking me to activate (don't think this means anything, just saying).

I check back today and I see that I can send feedback, same as in the picture in first post.

Same thing happened to me. I checked multiple times over the past two weeks to try to send feedback, but it kept asking for a key with no way around it. Now, its suddenly letting me send feedback with no problem. In 6956, I actually used a patch to bypass around this, so I cannot say for sure if there was a point where feedback got automatically turned on like this.

1 - 7 stars is poorly organised.

Eh, I kind of felt the same way when I first started sending feedback in 6956. This form is certainly could be better, but I can understand why they wanted to keep it simple so it does not deter beta testers from sending feedback in the first place.

That's odd; the Feedback window appeared for me in 6801 (with a Vista public beta key), and in 6956 and 7000 without keys.

Same for me as well. I just closed the key window and then next time it took me to that screen. It won't let me enter my product key though anyway.

Its changed I just sent feedback about a bug. I've no key...

lol...this is why anyone not in the beta shouldn't bother submitting "bugs"...

The "Send feedback" is NOT for submitting bugs...it's for general feedback about Windows 7.

If you enter a genuine KEY into the feedback tool when it asks, you get another feedback option, to actually submit a bug.

maybe they are releasing the real Beta soon, that's why they have activated the feedback?

It all comes back to MS knowing that unofficial beta testers could still provide valuable input through an even more diverse testing environments than what can be provided through the official testers. A smart move on their part since it is better to here what everyone has to say and get problems fixed while they can without ending up with backlashes later on how this or that slipped through and is causing errors with certain programs.

It asked me to enter my product key before, stating I could otherwise only send "limited" feedback - not none at all. I closed that, having no key, and there was an option to submit feedback with that exact form.

This was at least a week ago, so I'm gonna say that as far as I can see this is nothing new.

it has not always been active, you could not send feedback without entering a key, why would they create a dialog box if you could always get past it? They may have changed it, but only in the last week or so.

No, they have not. This dialog box has always been active.

No, they have not. This dialog box has always been active.

Please understand what i just wrote before. Before today you could not submit feedback without entering a key, Now you can send feedback by ignoring the dialog.

Of course the dialog box has always been active, it's designed into the OS lol :p

Please understand what i just wrote before. Before today you could not submit feedback without entering a key, Now you can send feedback by ignoring the dialog.

Of course the dialog box has always been active, it's designed into the OS lol :p

Erm, no. As I said, I have been able to submit feedback the whole time. You just had to close that dialog, like you said, and the option became available. Nothing changed recently.

I had the same also, i clicked cancel and then clicked the link again and i was able to download configuration and submit feedback.

post-698-1231194357_thumb.jpg

That only shows up to the 30th of Dec since i formatted then. I submitted lots before that also.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, another half hour unpacking and setting up the smart scope + tripod for equatorial tracking, then 15 more minutes mucking around with settings and shooting calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. Even with a smart scope like Dwarf 3, regular non-astro photography is still way more approachable to people getting into photography. I find this is a time consuming niche no matter how I go about it. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself in addition to everything else. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
    • Getting further away from the artistic study of mental disease that was the first game... (which never needed any sequels to begin with) But I get it, a company has to make money. And the second was at least visually impressive, if not in any other way.
    • If its the devs fault you would think Unreal would help M$ take full advantage of Unreal and work with them to fix the performance issues. Otherwise they are catching unwarranted bad press.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!