 Like the new testcase for WSL on the QA site - clear concise instructions - http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/246554/testcases
 folks, is it just me or 'apt-get update' (or apt update) takes - forever. 
 And it's not downloading files, it's doing 'store', a process which uses 100% of cpu, and lasts for like 60-90 seconds
 What flavour? (re @MrkiMike: folks, is it just me or 'apt-get update' (or apt update) takes - forever. 
 And it's not downloading files, it's doing 'store', a process which uses 100% of cpu, and lasts for like 60-90 seconds)
 UbuntuMATE, this is 20.04, but I experience this on 21.10 (plain Ubuntu) too (I have it in KVM for some testing) (re @Leokolb: What flavour?)
 tested mate this am - no problems with update
 the updates work fine, it's just that this 'store' process runs very long
 ah..kvm - i am running barebone
 Why would there be a difference?
 possibly - maybe yr internet connection?
 maybe someone else has same problem ..
 That's why I'm asking here. It's not internet problem - again, it's the 'store' process that uses 100% cpu for over a minute.
 Just tested on Mate Jammy apt update 2 seconds on a dell opti 7040 box with ethernet connection (re @MrkiMike: That's why I'm asking here. It's not internet problem - again, it's the 'store' process that uses 100% cpu for over a minute.)
 Again, this has nothing to do with internet connection :)
 mario@BUNTOR ~> file /usr/lib/apt/methods/store
 /usr/lib/apt/methods/store: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=49729cefd509c904cb21134693875a05fbe43586, for GNU/Linux 3.2.0, stripped
 this is the process that is started by apt-get after it downloads all the package lists
 and that one lasts forever
 and now, desktop machine (well, this one is Neon, based on Ubuntu LTS), I can barely notice the store process starting
 I don't fully understand what that 'store' is, and why it takes so long (I see that it decompresses something...)
 Sorry @MrkiMike have never run into this myself .
 @MrkiMike cannot reproduce here, it could be a disk issue on your end or network slowness, do you have a minimally repeatable example that we can attempt the same processes?  from system setup to when you get your issue
 also apt is better than apt-get just saying ;)
 it could be a compression CPU usage - that uses CPU a lot if its compressing data at all