Win 10 in VM slow after first reboot - 100% disck usage

[Tom5678]

Hello everybody

I have ubuntu mate installed on USB 3.0 and then windows10 in virtualbox. Then I create a linked clone

When I boot the windows clone for the first time works great, without any problem but after turn it off (without installing nothing) and reboot, next day for example, works really slow. Take like 5 minutes for open the browser for example.
The problem is the 100% disk usage, in fact the usb pen doesn't stop flash. If I open the task manager there is nothing shown that use 100% of the disk.

What can be the problem?
Let me know if I need to post more details and which, in case

thank you

[Perryg]

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

[Tom5678]

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

Could you please let me know which part of the log I have to look? Also if there is some documentation on "how to read a VM log" I'll read it. I prefer to understand how it works instead of post everything here and get the solution.

thank you

[socratis]

Unfortunately there is no documentation on how to read the VBox.log. It takes months of observing other users' posts and analysis to understand the details of what's going on. So, please post the whole log as a ZIPped attachment and we'll take a look at it.

Let me take a wild guess and assume that if you do not launch the linked clone but the original, it work all right? And secondly, why do you use a linked clone? Just out of curiosity...

[Martin]

You are running your host os from an USB stick, and then there also a virtual machine from the same stick?
No USB stick is fast enough for a decent performace with such a usage.

[Tom5678]

I noticed that this appen only after installing the first time upgrades, so I just disable them from administrative tools/services/windows update and now the problem is fixed