WoeUSB-ng
                                
                                 WoeUSB-ng copied to clipboard
                                
                                    WoeUSB-ng copied to clipboard
                            
                            
                            
                        Policy was updated, please run this program again
Good Habit Checklist for Issue Reporting
Checkout Mastering Markdown · GitHub Guides if you needs help on the GitHub-flavored Markdown syntax. You may remove sections and contents that don't apply.
- [x] I've searched the issue tracker and is pretty sure that there's no duplicate issue already filed
- [x] I've built the latest development snapshot using the instructions in README and verified that the issue can still be reproduced (for bug reports)
Issue Reproduce Instructions
- Launch WoeUSB by running woeusbgui
Expected Behavior
No error
Current Behavior
WoeUSB errors with message Policy was updated, please run this program again
Info of My Environment
WoeUSB Version0 .2.10-2
For source code build, run
git describe --tags --always --dirtyunder the source tree, for prebuilt releases refer the source that provides WoeUSB
WoeUSB Source
Installed from pip on
Information about the Operating System
Different OS distributions provides different characteristics and may influence the result of running WoeUSB. Run
lsb_release --descriptionorlsb_release -din a terminal to acquire this information.
Information about the Source Media
"Windows 11 MULTI" downloaded from https://microsoft.com/download/windows-11
Information about the Target Device
GIGASTONE 16GB USB-2.0
Please provide all of the requested information, especially:
Information about the Operating System Different OS distributions provides different characteristics and may influence the result of running WoeUSB. Run
lsb_release --descriptionorlsb_release -din a terminal to acquire this information.
Try running it as root, the same problem happened to me (I'm using Fedora 36) when running via GUI or without privileges, but it worked doing this way. My guess is that this policy updater for some reason did not work. Maybe because I'm using Fedora?