Folders Resetting Themselves

This just started happening and since a reboot didn't fix it I'm stumped as to what is going on. When I have a folder open with enough files listed that I have to scroll through the list, every now and then, even though I'm still using the list, the folder resets itself to the beginning.

That's starting to happen several times within 10 minutes.
I can't think of anything running in the background that should affect folders or ask for some kind of screen refresh. (Running Creator's Update on Windows 10 Home on Dell XPS 8700.)

Any ideas?
Thanks.

That depends on exactly how are you scrolling. Do you click to lock on the scroll bar then move the pointer up or down to scroll?

If so, then that is normal behaviour. I've found that if the pointer moves too far horizontally to either side of the scroll bar then the link between the pointer and the scroll bar is lost, the scroll jumps back to its initial position. It's still locked, so move the pointer closer and it should jump back to where you had got to. Experiment to find out how far away from the scroll bar you can get before it happens.

If you are scrolling in some other way, please describe how you are doing it.

Not exactly sure I understand what you're describing, Bree. I usually click in the white space above or below the dark part of the scroll bar (which represents the current visible window of the folder). I want to move an equal number of windows in the folder which may have a thousand files while the window only shows around 25 files (depending on how large I stretch the window). If I use the snap to feature so that the open window takes up half the screen, then I can see about 26 files at a time.

I don't usually move the solid bar that represents the visible part of the folder since it's difficult to place it at exactly the next spot I want to appear in the window. I can get to exactly where I want to by clicking above or below that bar and counting the number of clicks it takes to see that part of the folder I'm interested in.
I"ve been navigating this way in my folders for at least 20 years and never had them return themselves to the top of the folder view before.

A little more details: What I'm doing is comparing two folders to each other to see what files are in one but not in the other. If I click four times in one folder then four times in the other folder I should see the same exact content window in both folders, if they are the same. It they aren't the same then I can see what is different and fix it by adding or deleting a file (or files) in whichever folder is not correct. The window should stay open showing whatever part of a folder I'm interested in comparing for as long as I want it to stay open. But the windows have started closing itself from my chosen view and returning to the top of the folder. It should wait for me to change that view not take it upon itself to change it.

I see what you are doing, what I was describing was dragging the solid bar (which is not what you are doing).

I have tried it your way and it works as you would expect it to. The only thing I can think of that could cause one of your windows to be redrawn is if some process is writing to one of the files in the folder while you are viewing it in Explorer. A change in the contents, even if it's only the date of last access, could be causing Explorer to refresh the view.

I guess it's obvious that something is causing the window to be refreshed. I just can't figure out what it could be.

If I'm working within two folders and they refresh the view, it does do both folders at the same time. I just move the visible windows back to where I was and continue checking them until they system decides to refresh them again. This is happening sometimes every five minutes or so. It slows me down considerably to have to keep repositioning the windows of both folders to the view I want.

I'm not changing anything to cause the refresh, Windows seems to be doing it on its own. Or there's some process working in the background that initiates the refresh. Might take a long time to figure out what's going on for sure. But it never happened before CU so I think it must be related to the update.