N
NormanFarrer
Guest
Since early February updates I have had several problems.
File Explorer keeps freezing, crashing, losing the images on the icons etc. I have sorted these out to some extend so things only go wrong about once a day which is better than the 6 or 7 time it was when it started. I have also found the Flexible Renamer utility freezes every time I try to run it.
I have had very little problem with windows 10 in the past but this batch of updates has caused so much aggro it is unreal. Surely after all these years microsoft should be able to get things right
Apparently from what I have read microsoft don't consider the File Explorer issues to be much of an issue, well they are wrong. It is a major issue that should never have happened and once it did it should have been sorted in days not weeks and still no solution.
As for the Flexible Renamer issue I believe this is related as it runs a file explorer system and other programs than do a similar thing when loading & saving files had similar issues.
Does anyone have a workable solution till microsoft gets their finger out?
Continue reading...
File Explorer keeps freezing, crashing, losing the images on the icons etc. I have sorted these out to some extend so things only go wrong about once a day which is better than the 6 or 7 time it was when it started. I have also found the Flexible Renamer utility freezes every time I try to run it.
I have had very little problem with windows 10 in the past but this batch of updates has caused so much aggro it is unreal. Surely after all these years microsoft should be able to get things right
Apparently from what I have read microsoft don't consider the File Explorer issues to be much of an issue, well they are wrong. It is a major issue that should never have happened and once it did it should have been sorted in days not weeks and still no solution.
As for the Flexible Renamer issue I believe this is related as it runs a file explorer system and other programs than do a similar thing when loading & saving files had similar issues.
Does anyone have a workable solution till microsoft gets their finger out?
Continue reading...