-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rufus 2.7 and later produce a notification sound when closed using X #893
Comments
Yes it is. Rufus disables Autorun while it is running, so that you don't get prompted by a Windows prompt/new Explorer window every time you plug an USB while it is running (since you are going to reformat that drive anyway), and it does so using Microsoft's official way, through the use of Local Group Policies (which ensures that, should your computer ever crash while the policy is being altered, it will remain in a known state). Now, while the modification of Local Group Policies might be logged (as thousands of other benign events, which Administrators might want to be able to track), I can tell you that the notification sound you hear is 100% due to your own customization, and does not occur on a standard installation of Windows (else, this would be an annoyance that would be reported over and over, and you'd be able to find plenty of similar reports in this issue tracker, especially as the code that deals with Local Group Policies hasn't changed one bit in many releases). Especially, changing Local Group Policies is not an event that requires users to be notified. So, if your computer does produce a sound every time a Local Group Policy is changed, then I would surmise that it's either because you configured that yourself, or you installed software that did that for you. If the latter, I would suggest you contact the makers of that software (probably a "security" solution or something similar), as there are plenty of legitimate reasons to for applications to want to alter Local Group Policies, such as temporarily disabling AutoRun, and "security" solutions, or other type of monitoring software, shouldn't really be making their users jump every time that happens. As I believe this should answer the question, I will close this issue. |
Hmmm, actually, after further testing, I can replicate the issue now on a regular Windows 10 installation (and this also seems to happen with the previous version). This only occurs when using I guess I'll need to take a look at it. Curious as to why nobody reported that issue until now. |
Looks like this behaviour with |
Issue was introduced in [4474642] and more specifically with the replacement of |
yeah...now i remembered that using the close button did not produce the sound. (sorry it slipped my mind) anyway hope it;s not big of a deal. |
Nah, it shouldn't be a big deal to fix, as I have a good idea of what needs to be reverted to prevent the closing sound. And I probably should have spent a bit more time testing your initial report before dismissing it... Anyway, it'll be fixed in the next version - thanks for the report! |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query. |
Checklist
Log
button in Rufus and copy/pasted the log into the line that says<FULL LOG>
below.Rufus version: x.y.z
- I have NOT removed any part of it.Additionally (if applicable):
#
button (at the bottom of the Rufus interface), to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied. I confirmed, by performing an internet search, that these values match the ones from the official image.Issue description
Log
Not an issue but basically an annoyance (don't know how to describe it)
Every time Rufus Starts or Exits it writes this into event log
"The Group Policy settings for the computer were processed successfully. New settings from 1 Group Policy objects were detected and applied"
And the second, Exiting Rufus makes a Notification sound in windows.
Is all this intended?
The text was updated successfully, but these errors were encountered: