Windows 10: Best method to setup 4 disk's 2x NMVE.2 and 2x HDD Disk's

Currently I have 4 Windows 10 and Windows 11 operating systems disk's on 1pc using boot manager that do 2 successful and 2 unsuccessful. They are 1X 1Tb and 1X 512GB NMVE.2 Disk's and 1X 3TB and 4TB HDD an total of 4 drives. Please advise if it is best to deactivate and uninstall all programs and do fresh start with Windows 11 on 1Tb or 512 GB, then all programs on the other drive. Then to use the documents etc. on the 3TB HDD and backup on the 4TB HDD. Alternatively use EaseUS or AMEI etc. to move programs to the selected NMVE.2 disk and documents etc to the other HDD.

:)

 

Can a SanDisk Ultra microSDXC UHS-1 Memory Card - 200GB be partitioned into 2x 100g disks for windows Lumia 1520

Can a SanDisk Ultra microSDXC UHS-1 Memory Card - 200GB be partitioned into 2x 100g disks for windows Lumia 1520

 

My new HDD is not showing up on disk manager, but shows up in BIOs

I tried doing that and the 4TB HDD (which would be disk 2 in this case) is not showing up in the disk list, just the first 2 disks aka disk 0 and disk 1

how would i do the rest of the steps if the HDD isn't in the CMD list disk at all?

https://cdn.discordapp.com/attachments/1024776034501001267/1062614641840242760/image.png

 

WPR.exe for Windows 10 uses 2x more CPU, RAM, Disk IOPs, and Disk Space vs. Xperf

Hello Windows Support, I would like to report a likely bug that is easily reproducible in Windows Performance Recorder and I like to see it fixed as this is an important tool for determining root cause analysis for OS & Application performance issues.

Problem:

• wpr.exe -start generalprofile -start cpu -start power -start diskio -start fileio -start minifilter uses 2x more CPU, RAM, Disk IOPS, and Disk Space then the same Providers used in Xperf.
  
• Customer workstations that already have significant CPU or Disk performance issues cannot use the above command because it is too system intensive vs. recording the same parameters using Xperf.exe This makes it very difficult to find root cause using WPR.exe to collect the ETL trace data necessary to determine what is occurring.
  

Repro Steps Prework: Getting your CPU, RAM, Disk, and Disk Space views via Task Manager and Windows Explorer

1. In an elevated CMD prompt run diskperf -y to enable Disk Metrics in Task Manager. Then Open up Task Manager / Performance and you should now see CPU, RAM and Disk Metrics on the left side panel and their usage numbers.
   
2. Have Windows Explorer configured for Details view and go to the Perflogs folder (you may have to elevate permissions to access this folder).
   
3. Now you are able to see in Real-Time the CPU, RAM, Disk IOPs (MB/sec impact) Disk Space used, and compilation time.
   
4. Run CHKDSK /f to generate some moderate load
   

Repro Steps:

1. On a Windows 10 machine (say 21H2 or 20H2) have the following elevated CMD prompt ready to run this command: wpr.exe -start generalprofile -start cpu -start power -start diskio -start fileio -start minifilter -recordtempto c:\Perflogs and run the command.
   
2. Generate some moderate system activity by running CHKDSK /f and then DXDIAG and allow it to finish in the GUI. This should take about 60-90 seconds depending on the # of CPU Core, the RAM available, and the class of storage (5400 rpm HD, SSD, NMVe).
   
3. Run wpr -stop c:\perflogs\SystemStressWPR.etl to start the WPR impact to the system to record and compile these ETL providers into a single .ETL file.
   
4. Immediately start a stop watch and watch Task Manager for CPU impact, RAM impact, and especially Disk MB/sec consumed, and also Disk Space used in the Windows Explorer view.
   
5. Now run the following (2) Xperf commands which grabs the same providers to make it a fair comparison with WPR in Step #1 above:
   
   "C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\xperf.exe" -on PROC_THREAD+LOADER+CSWITCH+FILENAME+Profile+Interrupt+DPC+Hard_Faults+Disk_IO+Disk_IO_Init+Split_IO+Perf_Counter+Power+MemInfo+MemInfo_WS+FILE_IO+FILE_IO_INIT+DRIVERS+FLT_IO_INIT+FLT_IO+FLT_FASTIO+FLT_IO_FAILURE -stackwalk CSwitch+DiskFlushInit+DiskReadInit+DiskWriteInit+KernelQueueEnqueue+KernelQueueDequeue+Profile+ReadyThread+FileCreate+FileCleanup+FileClose+FileRead+FileWrite+MiniFilterPreOpInit+MiniFilterPostOpInit -BufferSize 2048 -MaxBuffers 2048 -MaxFile 4096 -FileMode Circular -f c:\Perflogs\kernel.etl
   
6. Then immediately run the User mode Provider collection to match the WPR switches above - this is logged as User.etl
   
   "C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\xperf.exe" -start User -on 8c493695-3df4-40cb-b11d-9edc41d5d2ab:0x0:0x4:'stack'+9580d7dd-0379-4658-9870-d5be7d52d6de:0x0000000000000200:0xff:'stack'+0a002690-3839-4e3a-b3b6-96d8df868d99:0x0:0x5:'stack'+d8975f88-7ddb-4ed0-91bf-3adf48c48e0c:0x0:0x4:'stack'+bf406804-6afa-46e7-8a48-6c357e1d6d61:0x0000000000000003:0xff:'stack'+49c2c27c-fe2d-40bf-8c4e-c3fb518037e7:0x0:0xff:'stack'+e7ef96be-969f-414f-97d7-3ddb7b558ccc:0x0000000000002000:0xff:'stack'+315a8872-923e-4ea2-9889-33cd4754bf64:0x0000000000100000:0x4:'stack'+36b6f488-aad7-48c2-afe3-d4ec2c8b46fa:0x0000000000010000:0xff:'stack'+d49918cf-9489-4bf1-9d7b-014d864cf71f:0x0:0xff:'stack'+331c3b3a-2005-44c2-ac5e-77220c37d6b4:0x0000000000000004:0xff:'stack'+57277741-3638-4a4b-bdba-0ac6e45da56c:0x0000000000000001:0xff:'stack'+e13c0d23-ccbc-4e12-931b-d9cc2eee27e4:0x0000000000000098:0x5:'stack'+751ef305-6c6e-4fed-b847-02ef79d26aef:0x0:0xff:'stack'+cfeb0608-330e-4410-b00d-56d8da9986e6:0x0:0xff:'stack'+8e92deef-5e17-413b-b927-59b2f06a3cfc:0x0:0xff:'stack'+e4b70372-261f-4c54-8fa6-a5a7914d73da:0x0:0xff:'stack'+83ed54f0-4d48-4e45-b16e-726ffd1fa4af:0x0:0xff:'stack'+6ad52b32-d609-4be9-ae07-ce8dae937e39:0x0:0x4:'stack'+8c416c79-d49b-4f01-a467-e56d3aa8234c:0x0000000000402000:0xff:'stack'+e6835967-e0d2-41fb-bcec-58387404e25a:0x0000000000000001:0xff:'stack'+a669021c-c450-4609-a035-5af59af4df18:0x0000000000000118:0x0:'stack'+8c416c79-d49b-4f01-a467-e56d3aa8234c:0x0000000000080000:0xff:'stack'+e7ef96be-969f-414f-97d7-3ddb7b558ccc:0x0000000000080000:0xff:'stack'+0f67e49f-fe51-4e9f-b490-6f2948cc6027:0xffffffffffffffff:0xff:'stack'+2a274310-42d5-4019-b816-e4b8c7abe95c:0x0000000000000010:0xff:'stack'+a6ad76e3-867a-4635-91b3-4904ba6374d7:0x0000000000000010:0xff:'stack'+ce8dee0b-d539-4000-b0f8-77bed049c590:0xffffffffffffffff:0xff:'stack'+c4636a1e-7986-4646-bf10-7bc3b4a76e8e:0xffffffffffffffff:0xff:'stack'+1babefb4-59cb-49e5-9698-fd38ac830a91:0xffffffffffffffff:0xffffffff:'stack'+8E9AC05F-13FD-4507-85CD-B47ADC105FF6:0xffffffffffffffff:0xffffffff:'stack'+DEDADFF5-F99F-4600-B8C9-2D4D9B806B5B:0xffffffffffffffff:0xffffffff:'stack'+A103CABD-8242-4A93-8DF5-1CDF3B3F26A6:0xffffffffffffffff:0xffffffff:'stack'+F5D05B38-80A6-4653-825D-C414E4AB3C68:0xffffffffffffffff:0xffffffff:'stack'+6B4DB0BC-9A3D-467D-81B9-A84C6F2F3D40:0xffffffffffffffff:0xffffffff:'stack'+C4636A1E-7986-4646-BF10-7BC3B4A76E8E:0xffffffffffffffff:0xffffffff:'stack'+CB587AD1-CC35-4EF1-AD93-36CC82A2D319:0xffffffffffffffff:0xffffffff:'stack'+cc7b00d3-75c9-42cc-ae56-bf6d66a9d15d:0xffffffffffffffff:0xffffffff:'stack'+90742496-54a9-4075-8079-425399080068:0xffffffffffffffff:0xffffffff:'stack'+Microsoft-Windows-TCPIP:0xffffffffffffffff:0xffffffff:'stack' -BufferSize 2048 -MinBuffers 2048 -MaxBuffers 2048 -MaxFile 4096 -f c:\Perflogs\User.etl
   
7. Repeat Steps #2-4
   
8. Now stop the Xperf ETL capture by running the following command: xperf.exe" -stop -stop User -d c:\Perflogs\%computername%_SystemStressXperf.etl
   
9. You will observe that the CPU impact, RAM impact, Disk MB/sec consumed, and also Disk Space used is at least 2x less using Xperf vs. WPR.
   
10. WPR used to be as lightweight as Xperf, so the bug is that it is now 'bloatware' and is now 2x slower and uses 2x more disk space to do the same work that it's predecessor can accomplish.
    

Desired Outcome:

Make WPR as fast and as lean as Xperf as it used to be.

Screenshots:
Observe that Xperf compiled on my system 3x faster and only used 648MB vs. 1.7GB for the exact same data in WPR. Why the resource and file bloat to use WPR?