Version 4.17 Freezes after every batch!?
Every time I run a script, the program freezes and must be killed from the OS (Windows 11 Pro, Version 24H2).
It freezes on the "Progress" screen like so: https://i.postimg.cc/mg4vjV2b/Aren-portable-freezes-after-ev ery-batch.png
None of the buttons on that dialog work and it will not close.
The problem also occurred in version 4.16 but, since I couldn't use that version anyway, I wasn't overly worried.
Anybody else see this on Win Pro 24H2?
How do we fix it?
It freezes on the "Progress" screen like so: https://i.postimg.cc/mg4vjV2b/Aren-portable-freezes-after-ev ery-batch.png
None of the buttons on that dialog work and it will not close.
The problem also occurred in version 4.16 but, since I couldn't use that version anyway, I wasn't overly worried.
Anybody else see this on Win Pro 24H2?
How do we fix it?
Reply to #1:
Hi Randy,
I'm running that version and have had no freezes.
I've only run small batches of files and folders, maybe 10 to 15 batches in all, but nothing like that.
EDIT: I'm using the installed version. I haven't seen any differences in the two versions previously, though. END EDIT
Best,
DF
Hi Randy,
I'm running that version and have had no freezes.
I've only run small batches of files and folders, maybe 10 to 15 batches in all, but nothing like that.
EDIT: I'm using the installed version. I haven't seen any differences in the two versions previously, though. END EDIT
Best,
DF
Reply to #2:
Thanks. I'm still poking around here trying to figure it out. And don't have a lot of time for that at the moment.
Update: Is it stalling out trying to write a file, registry entry or send telemetry?
Does it require a service I've disabled?
PS. I did try the installed version (after making a restore point). No dice; had to revert.
Thanks. I'm still poking around here trying to figure it out. And don't have a lot of time for that at the moment.
Update: Is it stalling out trying to write a file, registry entry or send telemetry?
Does it require a service I've disabled?
PS. I did try the installed version (after making a restore point). No dice; had to revert.
Reply to #1:
I can take a look at it. Can you save your methods to a .aren file and sent it to me? It helps me narrow down where to look.
I also need to know the type of files you are renaming.
I can take a look at it. Can you save your methods to a .aren file and sent it to me? It helps me narrow down where to look.
I also need to know the type of files you are renaming.
Reply to #4:
Thanks. Sent email an email.
Thanks. Sent email an email.
Reply to #5:
Per email exchange with Kim, this problem now appears to be because Aren, version 4, does not play nice with FancyZones.
Temporarily turn FancyZones off (NOT a viable solution) and Aren does not stall. This is the first time I've seen this out of at least a hundred apps over the years.
Per email exchange with Kim, this problem now appears to be because Aren, version 4, does not play nice with FancyZones.
Temporarily turn FancyZones off (NOT a viable solution) and Aren does not stall. This is the first time I've seen this out of at least a hundred apps over the years.
Reply to #6:
Wow, bummer dude. I think I tried that a while back. Along with a bunch of other "window managers". As far as I know there's nothing that does the only window management I want: on restart restore everything to *just* the way it was when I shut down. Oh well.
Wow, bummer dude. I think I tried that a while back. Along with a bunch of other "window managers". As far as I know there's nothing that does the only window management I want: on restart restore everything to *just* the way it was when I shut down. Oh well.
Reply to #7:
Actually FZ does do that pretty well for me, at least for the apps that are configured to start on start/login.
Some exceptions are things like Task manager and programs that are showing errors.
But even if something's not where I want it, I just focus the window, press one hotkey and bam. It's perfect in less than a second per window.
You could write a PowerShell script to do what you want on a restart that wasn't due to a crash or app/windows hijacking.
ETA: Also sounds like what you want is "Hibernate" mode ;)
https://www.guidingtech.com/how-to-enable-and-use-hibernate- mode-on-windows-11/
I use the s**t out of that on my windows laptops.
Actually FZ does do that pretty well for me, at least for the apps that are configured to start on start/login.
Some exceptions are things like Task manager and programs that are showing errors.
But even if something's not where I want it, I just focus the window, press one hotkey and bam. It's perfect in less than a second per window.
You could write a PowerShell script to do what you want on a restart that wasn't due to a crash or app/windows hijacking.
ETA: Also sounds like what you want is "Hibernate" mode ;)
https://www.guidingtech.com/how-to-enable-and-use-hibernate- mode-on-windows-11/
I use the s**t out of that on my windows laptops.
Reply to #8:
I just leave it running all the time. :)
Then I just have to deal with when Windows shuts down for updates. Not a big deal.
Best,
DF
I just leave it running all the time. :)
Then I just have to deal with when Windows shuts down for updates. Not a big deal.
Best,
DF
Reply to #6:
I installed FanzyZones in a VM and played around with it while doing some batches with Advanced Renamer. I did not experience any issues. I also tried various settings of FancyZones, but did not find any that would reproduce this behaviour. I don't know how to help you.
I installed FanzyZones in a VM and played around with it while doing some batches with Advanced Renamer. I did not experience any issues. I also tried various settings of FancyZones, but did not find any that would reproduce this behaviour. I don't know how to help you.
Reply to #10:
I have an idea that might help. The progress window starts out in a non-sizeable mode and when the batch completes it becomes sizeable. That change in window mode might be confusing FancyZones. For the next version I will let the window start in the sizeable mode. It is a little weird with a sizeable progress window, but it is not the end of the world.
FYI I will also fix that the actual progress bar is too wide for the window (if anyone noticed).
I have an idea that might help. The progress window starts out in a non-sizeable mode and when the batch completes it becomes sizeable. That change in window mode might be confusing FancyZones. For the next version I will let the window start in the sizeable mode. It is a little weird with a sizeable progress window, but it is not the end of the world.
FYI I will also fix that the actual progress bar is too wide for the window (if anyone noticed).
Reply to #11:
Thanks Kim,
I'll try to come up with a recipe to duplicate the issue in a VM in the coming days. But I also have to pay the bills and tend house.
It may be a a combination of things like FancyZones and that I have both windows screen and text magnifications turned on. Every other app beats up on us "Seasoned Citizens" and our failing, bloodshot eyes. ;P
Thanks Kim,
I'll try to come up with a recipe to duplicate the issue in a VM in the coming days. But I also have to pay the bills and tend house.
It may be a a combination of things like FancyZones and that I have both windows screen and text magnifications turned on. Every other app beats up on us "Seasoned Citizens" and our failing, bloodshot eyes. ;P
Reply to #12:
Update: Been busy since I posted the above, so forgot to mention. It turns out that FancyZones has an "Excluded apps" setting. Adding ]aren.exe[ (without the brackets), band-aids over the problem for now.
Update: Been busy since I posted the above, so forgot to mention. It turns out that FancyZones has an "Excluded apps" setting. Adding ]aren.exe[ (without the brackets), band-aids over the problem for now.