Once you open it again, it's fine, but if you try to preview 3D Files, you quickly run out of CPU. Thanks for the information! This is super useful.Įdit: One way to get the processes back is to close the instance of explorer. I will report this to the Windows team tomorrow. A huge spike to the CPU caused by the preview handler trying to load large 3D objects in preview.

When loading them, I didn't notice a hit to my RAM usage, but I did see exactly what you saw. The files loaded slowly, but once they were loaded, the application was quick. I did the test you suggested on a GTX660 on an old hard drive disk with 32G of Ram. It's funny, when a good tip is just revert his purpose 'from it so nice.' to. That's why it important to remove all the format file associated with view 3d app. Quite nice at first time, but honestly do not use that win 10 preview, the processes behind the feature will hang on and will drive your cpu to run at 99% just because a file can't to get read, or the version of the file isn't compatible, or again because the file is too big and the app can't to handle the preview.Īfter you associate the obj fbx,format files with view 3d app you will simply run into an endless loop everytime explorer try to preview a 3d file format, and you would again have to lkill the process manually.

Quick preview on windows