Fences 4.07.01 Beta Feedback Thead » Forum Post by sdrohan

Quoting big4,

When I access the directory inside the fence while pressing win+space, no subdirectories are displayed. In the product version fenc4, subdirectories are displayed stably.

Hello,
Sorry to hear you are having issues. May we know more details please.

Windows 10 or 11? And its full version numbers. Use Winver.exe to get those.
Post a video of this issue and post its link here.

Thanks
Basj,
Stardock Community Assistant.

Successfully updated karma reason!

Windows 10 Pro

21H2

19044.1865

Fences4_retail

https://youtu.be/gF84wye1fFo

Fences_4.05.21-j75

https://youtu.be/Q00X66c13W4

Successfully updated karma reason!

Thanks for the video, but I can't reproduce your issue on my system.

Please try purge and reinstall steps as mention here : [Link]. Just make sure to redownload the latest version from your account page. Reboot after the purge. Reinstall and reboot again after the installation. Retest and report back here.

Thank you,
Basj,
Stardock Community Assistant.

Successfully updated karma reason!

Launched Purge_Fences.bat and uninstalled successfully.

Again, I pressed the beta download button from My Downloads and installed it newly.

But Fences_4.05.21-j75 doesn't work properly.

It works fine if I over install Fences4_retail.

The linked video can be seen when accessed from Japan.

However, if you can't see it there, I will upload the following two files and provide them to you, so please let me know the URL where your company can upload them.

I will upload the working status soon.

Fences4_retail.mp4(1,289KB)

Here is a working video.

Fences_4.05.21-j75.mp4(4,364KB)

is an incorrect behavior.

Successfully updated karma reason!

I saw your two video without issue here.

Quoting big4,

reply 55

But Fences_4.05.21-j75 doesn't work properly.

It works fine if I over install Fences4_retail.

Not really sure on what do you mean by this? What error appear when you install "Fences_4.05.21-j75-Setup_sd.exe"?

Thank you,

Basj,
Stardock Community Assistant

Successfully updated karma reason!

After Launched Purge_Fences.bat works,

As a result of reinstalling it, fence4 works poorly.

1. It is a new installation.

However, the default My Documents and Program files do not appear on the desktop with a fence around them.

2. Selecting a folder and right-clicking to choose shou this folder on the desktop does not work.

It seems broken.

Please tell me how to restore it.

Successfully updated karma reason!

Okay, what I get from your comment about. The purge work, yes?

But after reinstalling. Which version? The "Fences_4.05.21-j75-Setup_sd.exe"? Did you reboot after the purge and after that installation?

Thank you,

Basj,
Stardock Community Assistant

Successfully updated karma reason!

Write only the conclusion.

Fences4_setup_sd.exe (Fences4_retail)

installed it works fine.

Fences_4.05.21-j75-Setup_sd.exe

installed will not work properly.

No error is displayed.

Compare the two actions below.

Both are fences with the same folder structure.

Fences_4.05.21-j75 works with win+space or win+D

Every time I dive into a subfolder, the subfolder that should be there disappears.

but,

Fences4_retail (Fences4_setup_sd.exe)

https://youtu.be/gF84wye1fFo

Fences_4.05.21-j75(Fences_4.05.21-j75-Setup_sd.exe)

https://youtu.be/Q00X66c13W4

If anyone is fluent in English, please follow those differences.

Successfully updated karma reason!

I'm sorry. Ignore Reply #57.
Please delete this comment as it is incorrect. For now, use Fences4_setup_sd.exe which is stable. Thank you very much.

Successfully updated karma reason!

Dear basj

really sorry. I realized that the translation was writing bullshit that had nothing to do with my intentions.

I realized that what I wanted to say in reply#59 is a phenomenon specific to my environment.

In my environment, after operating win+space and win+d with Fences_4.05.21-j75.exe, clicking a directory causes a problem that subdirectories that should be there disappear.

However, Fences4_setup_sd.exe does not have the same phenomenon.

This phenomenon is only in my personal environment, so it is wrong to ask others for universality.

For the time being, I will use Fences4_setup_sd.exe in my environment.

All Reply #49, 50, 52, 54, 56, 58, 59 I posted are wrong.

Please delete all of them, as they are a nuisance to developers and other customers.

Thank you.

Successfully updated karma reason!

Dear basj

For reference, I will let you know my environment and PC configuration.

Maybe it has something to do with having four screens on one PC.

Operating System

Windows 10 Pro 64-bit

21H2

19044.1865

CPU

Intel Core i9 @ 3.60GHz

Kaby Lake 14nm Technology

RAM

32.0GB

Motherboard

Micro-Star International Co. Ltd. MPG Z390 GAMING PRO CARBON AC (MS-7B17) (U3E1)

Graphics

EV2450 (1920x1080@59Hz)

EV2450 (1920x1080@60Hz)

2047MB NVIDIA GeForce RTX 3080 (MSI)

Storage

3726GB Samsung SSD 860 QVO 4TB (SATA (SSD))

3726GB SanDisk SDSSDH3 4T00 (SATA (SSD))

Thank you.

Successfully updated karma reason!

Dear basj

No feedback is needed as this is only happening in my environment.

Additional information will be provided for your reference.

Both Fences_4.05.21-j75-Setup_sd.exe and Fences4_setup_sd.exe

Selecting a folder, right clicking and selecting this folder on the desktop may or may not work. It often doesn't work.

Thank you.

Successfully updated karma reason!

Quoting big4,

reply 62

Dear basj

No feedback is needed as this is only happening in my environment.

Additional information will be provided for your reference.

Hello,
I have forward your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Successfully updated karma reason!

I understand.
I will monitor this thread and wait for updates.
Thank you.

big4

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+650

All,

We have updated the beta and 4.07.01 is now available:

https://forums.stardock.com/512519/get;3852518

Thanks again for all your feedback.

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

Quoting sdRohan,

reply 2

Known issues

While we appreciate all feedback, please remember that we offer no official support for beta \ preview \ developer channel versions of Windows. If you report issues while in any of those early release channels, you should not expect them to be addressed unless it still exists in a retail version of Windows.

Object Desktop Manager will read that there is an update after you have already done so when there is not. It will be fixed in the coming days.
Fixed

Umm... what about issues that have existed since Fences 3 and are still not fixed in any version of Fences 4, like the annoying resolution bugs detailed in this thread? (i.e. the only reason I paid money for an upgrade to a product that otherwise met my needs before). Shouldn't they be listed in the Known Issues reply?

Successfully updated karma reason!

Quoting kungfujoe,

reply 66

Umm... what about issues that have existed since Fences 3 and are still not fixed in any version of Fences 4, like the annoying resolution bugs detailed in this thread? (i.e. the only reason I paid money for an upgrade to a product that otherwise met my needs before). Shouldn't they be listed in the Known Issues reply?

Which resolution bug are you referring to? The only one I know of so far is the one when the monitors were dynamically added/removed/resolution changed (which I think was the main one that affected most of the other people according to other thread(s), but for that instance, it was resolved to be not a resolution issue but the following:

Fixed Folder Portal crash when details-view is used alongside multiple levels of sorting.

And from what I read in this thread only, the other resolution(s) was due to outdated Intel drivers, and some trying to use fences in a directory that is cloud-synced, which may not work best especially if the desktop was also synced in other machines.

Successfully updated karma reason!

Dear sdRohan

beta and 4.07.01

Thank you for your improvement work.

But there are two glitches.

See video below.

win+arrow_freeze.mp4
https://youtu.be/64Dhb0eLtSI

arrow_Double click_hoisting.mp4
https://youtu.be/FSz1-7VANFs

THANK YOU

Successfully updated karma reason!

Dear sdRohan

beta and 4.07.01

sorry.
The operation to climb the direction was alt+arrow, not win+arrow.
However, even if win+arrow is an erroneous operation, it is inconvenient to freeze.
On another note, I thought it was an error to double-click the directory arrow to wind up, but it was normal.
But it's unnatural.
What the user expected was that double-clicking the directory arrow would open that folder.

Other than those, it works fine.
This is a completely different story, but on my personal computer in a different environment,
there are 4 screens per unit, and only the icon is displayed in the foreground with win+d and win+space. Others are hidden in the back.
Only that computer is reproduced every time. Please let me know if there is a way to improve it.

THANK YOU

Successfully updated karma reason!

Quoting k3nny5,

reply 67

Which resolution bug are you referring to? The only one I know of so far is the one when the monitors were dynamically added/removed/resolution changed (which I think was the main one that affected most of the other people according to other thread(s), but for that instance, it was resolved to be not a resolution issue but the following:

Fixed Folder Portal crash when details-view is used alongside multiple levels of sorting.

And from what I read in this thread only, the other resolution(s) was due to outdated Intel drivers, and some trying to use fences in a directory that is cloud-synced, which may not work best especially if the desktop was also synced in other machines.

I saw what bug was fixed in the new beta, which is why I was specifically replying to the "known issues" message, not what was fixed.

I'm referring to the long-running problem where Fences screws up container positions after a driver update re-initializes the screen on high resolution monitors (i.e. it didn't happen when I was using monitors with resolutions of 1920x1200 and lower, but now, Fences shrinks the containers to a 1920x1200-sized box after every single GPU driver update). The problem has been present in Fences for years, and it has nothing to do with outdated drivers, Intel or otherwise. It's just the opposite - it's a problem that Fences causes when a user is ensuring that they're not using outdated drivers.

I figured it was a no-brainer that a major update like Fences 4 would address this problem, but 4.00, 4.05, and 4.07 have been released with no fix, and I was a little surprised (disappointed) to see that the "known issues" post claims that the Fences team is not acknowledging any known bugs in the software. If the devs really think 4.07 is perfect and bug free, why is it still in beta?

(I may have another one to report at some point, with respect to certain full-screen games intermittently kicking back to the desktop immediately upon running, but I haven't conclusively narrowed that down to Fences yet... but if it is a Fences problem, it's another one that's persisted since at least version 3)

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+650

Quoting kungfujoe,

reply 70

I'm referring to the long-running problem where Fences screws up container positions after a driver update re-initializes the screen on high resolution monitors (i.e. it didn't happen when I was using monitors with resolutions of 1920x1200 and lower, but now, Fences shrinks the containers to a 1920x1200-sized box after every single GPU driver update). The problem has been present in Fences for years, and it has nothing to do with outdated drivers, Intel or otherwise. It's just the opposite - it's a problem that Fences causes when a user is ensuring that they're not using outdated drivers.

A video driver update is kind of a big deal - it totally refreshes the display and restarts many running Windows services - my point, it's a rather disruptive act. That one may have to restore a Fences snapshot \ reboot when doing any video driver update may be what someone has to do with every update - something that is rather infrequent already.

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

about Reply#69

On my computer in another environment,
There are 4 screens per unit, with win+d and win+space bringing only icons to the front. Others are hiding behind.
I have resolved this issue myself. The cause was out of memory. When I expanded from 16G to 48G, the same phenomenon did not occur.

Winkey + D blank portal for Fences folder is completely gone in my environment.

Thank you very much.

Successfully updated karma reason!

Quoting kungfujoe,

reply 70

I saw what bug was fixed in the new beta, which is why I was specifically replying to the "known issues" message, not what was fixed.

I'm referring to the long-running problem where Fences screws up container positions after a driver update re-initializes the screen on high resolution monitors (i.e. it didn't happen when I was using monitors with resolutions of 1920x1200 and lower, but now, Fences shrinks the containers to a 1920x1200-sized box after every single GPU driver update). The problem has been present in Fences for years, and it has nothing to do with outdated drivers, Intel or otherwise. It's just the opposite - it's a problem that Fences causes when a user is ensuring that they're not using outdated drivers.

I figured it was a no-brainer that a major update like Fences 4 would address this problem, but 4.00, 4.05, and 4.07 have been released with no fix, and I was a little surprised (disappointed) to see that the "known issues" post claims that the Fences team is not acknowledging any known bugs in the software. If the devs really think 4.07 is perfect and bug free, why is it still in beta?

(I may have another one to report at some point, with respect to certain full-screen games intermittently kicking back to the desktop immediately upon running, but I haven't conclusively narrowed that down to Fences yet... but if it is a Fences problem, it's another one that's persisted since at least version 3)

To their benefit, Known issues in this beta thread may mean issues/regressions that arose since the last beta version was released (i.e. bugs introduced since 4.07). It doesn't necessarily mean bugs since its entire history/stable release/older releases. Beta releases (this one was released not too long ago), gives us the chance to test it out to see if it works and/or see if any new bugs came about as of result of the update. Beta is generally opted-in by users, thus generally less overall users in beta than stable, so theoretically less users impacted if something were to break.

Successfully updated karma reason!

sdrohan

Join Date 10/2012

+650

Quoting big4,

reply 72

Winkey + D blank portal for Fences folder is completely gone in my environment.

Thank you very much.

You are most welcome - than you for the update.

Sean Drohan
Stardock Product Lifecycle Manager

Successfully updated karma reason!

Quoting sdRohan,

reply 71

A video driver update is kind of a big deal - it totally refreshes the display and restarts many running Windows services - my point, it's a rather disruptive act. That one may have to restore a Fences snapshot \ reboot when doing any video driver update may be what someone has to do with every update - something that is rather infrequent already.

And yet, if Fences isn't installed, none of that is necessary. Hasn't been necessary since before Windows 7. It's not even necessary with other apps that overlay on the screen. They don't have this problem, nor does the OS, and nor do the drivers. Fences does, and has for years.

Regardless of whether the devs can figure out how to fix it, it should at least be logged as a known bug.

Successfully updated karma reason!