Bug with Scheduled Tasks and Start Menu Shortcuts not being added #85
Replies: 3 comments 2 replies
-
|
Also, on these failed machines, they also only have a logs folder in this location and that folder only has the install log because updates haven't happened yet due to it being broken. All other files (PS scripts, includedapps, etc) and folders (config, icons, mods, etc.) are missing. Path: C:\ProgramData\Winget-AutoUpdate Running newest version you have out, 1.06.0036, which is winget aas version - 1.21.13 |
Beta Was this translation helpful? Give feedback.
-
|
There seems to be a flaw in the logic of the Refresh-WingetConfiguration.ps1 powershell script. This is why scheduled tasks and start menu items aren't getting created. It has to do with this specific if/else statement: So the issue is that the variable $commandLineArguments actually equals the variable $previousCommandLineArguments, so it skips the creation of the scheduled tasks and start menu items. And as I stated above, all of the stuff that should be in "C:\ProgramData\Winget-AutoUpdate" isn't there, all files and folders are missing except for the "log" folder in that location. I have completely reconfigured the logic so that it checks for the scheduled tasks and creates them if they don't exist, regardless of the value of $commandlinearguments. I also added logic to check for start menu folder and icons add the start menu icons back, both of those functions are outside of the if/else statement so that it always runs. It now does what it should, creates the tasks and start menu items, however, I had to copy all the files for "C:\programdata\winget-autoupdate" manually. And still when I run, it bypasses the whitelist even though the registry settings are all correct from the GPO showing to use a whitelist and no blacklist setting set. No matter what it still just acts as if UseWhitelist isn't enabled when it is. In the logs it also says: WAU uses Black List config but it isn't set to do that. I have quite a bit of machines in this state where WAU is just straight broken on them and no matter what you do, it uses a blacklist instead of a whitelist as it is set to do. Not sure what is broken with this fork, but something definitely is. It's random whether it deploys correctly to a mass number of machines or is broken on them. I haven't gotten a response to this after a few days. I guess I don't have much of a choice except abandoning this project and going back to the original WAU from Ramanitho. It now has GPO support too and is updated much more often. |
Beta Was this translation helpful? Give feedback.
-
|
@Weatherlights can you give an answer on this? @WalterSobchak9515 were you able to solve this problem? I am having the same problem |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
As the title states, there is a bug where the start menu shortcuts don't get added and the scheduled tasks don't get created randomly. However, the GPO's are being applied successfully, for instance if you check the registry the startmenushortcut is set to 1. Randomly works for some machines, randomly doesn't for others.
It was described here: Romanitho#764
Any fix for that yet?
Beta Was this translation helpful? Give feedback.
All reactions