Hardware Reserved Memory 5.5GB

stephen said:

Sounds like good advice, do you think given time Microsoft updates would fix this type of thing ?
I'm not confident I know what I'm doing, but I'll read the guides and if I have any questions, I know where to come .... thanks

I highly suspect the problem you are seeing is directly related to having seen a buggy upgrade which has been seeing any number of odd ball type problems appearing for different people. Back when Vista saw it's first service pack that was to correct a goof that was made by MS developers as far as reporting the total amount of memory installed accurately. Vista also saw the 2gb only mandate for seeing the 64bit flavor of that version go on without problems being second in line from XP Pro x64 only seeing a little bit more support!

As for the guides if you follow the steps closely you should see working results without a problem since they are well written and easy to follow.

Just be sure any extra storage drive is unplugged when ready to see the clean install taken care of so you don't run into what a number of other people have already like I did. Unlike what you typically see with older versions as far as simply having the OS drive as the first in the order the 10 installer seems to get confused with other drives present and can end up placing the boot files and temp installation folders on the wrong drive(s)!

mihomilo said:

Hey i did a clean install of the 64bit windows 10. Turn out that i installed the wrong windows. Thanks for the help :).

Quick Fix for you! This is why I had to initially ask if you had unintentionally installed the 32bit 10 instead since you had seen to a clean install following the initial upgrade there. Now that you know were to look to check on that I doubt you will be allowing that to happen again!

Here I downloaded both flavors for both editions while I am a 64bit only person. With multiple upgrades I not only saw four flash drives made up for each but also burned four dvds and made up two 4 in 1 combination drives one being USB 2.0 with other being a 3.0 both 16gb in size which allows for additional files.

If you feel comfortable doing your own system tweaking I would suggest this advice provided on this website: Top 10 Ways to Fix High RAM/CPU Memory Usage after Windows 10 Update | Drive The Life Do perform steps 1(return this registry "VALUE DATA") entry back to 0 after restart)thru 10, exclude step 2, as that is a download that you do not need at this time. After all that
go to trusted site by Black Viper for advice on your win 10 operating system Services configuration for normal ops and set your services according to Mister Vipers suggestions. His website is here: Black Vipers Windows 10 Service Configurations » Black Viper | www.blackviper.com Some of these suggestions if not down properly could render your operating system un-usable, USE AT YOUR OWN RISK. However, I have used the advice given here and personally have not caused any problems to my own system and in fact this advice has significantly improved performance and reduced the load on memory to a negligible amount . Best of Luck.

I remember when 256Mb was a lot of ram and you could upgrade to 512 for about 150 bucks (maybe more). Just sayin.

I would say since one was simply the wrong flavor of the 10 clean install going on while the other has to do with a bug appearing in the upgrade install. The ultimate best solution of course would simply be to replace the upgrade with a fresh clean install as I had to do here back in July and so far 10 has been running pretty much bug free.

There are other options besides the MC tool like Rufus or the one used here since 7 was new being UltraISO for seeing iso images written to flash drives or burned to disk which UltraISO Free Trial can do both as well as create new disk images.

To use one of those two you need to skip the upgrade now, create usb media, and lastly the option to burn to dvd unless you have a blank you can toss in to see how that will come out. Otherwise you would want to save the "Windows.iso" download and even rename as you save it to "Windows 10 Home or Pro x86 or x64 .iso" so you can identify it in case you should decide to go back again.

Once you have a clean install on the Reset option will be more likely to succeed over trying it from a buggy upgrade where things never seemed to have gone on fully. You could try but risk an unusable form of 10 if that option got trashed by an incomplete install of 10 during the upgrade. If the WS folder remains on the drive you then have the immediate repair install potion by simply starting up the setup.exe file. You find that in "C:\$Windows~WS\Sources\Windows" if the WS folder is present since that is the 64bit's temp install folder seen there while the BT is for language packs only. The 32bit only sees the BT folder.

You can try again at seeing the Media Creation Tool make up the flash drive a second time or use another program entirely to see the 10 installation media made up. First you simply bypass all of the other options to see the edition you are running downloaded and saved to a folder as you would with any other download.

Once you have the "Windows.iso" unless you rename that to the edition name you simply use one of the other programs to see the 10 install key made up. Here I simply have stayed with UltraISO now for about 7 1/2yrs. before 7 was even out for use with Vista the first time I tried that one out.

Once you have the new 10 media up you boot live from that in order to select the "Custom" install option not the upgrade and proceed to replace the buggy upgrade with a fresh clean install of 10. The Clean Install guide is what to follow since that will take you through each step with ease! There's nothing too complicated since all you have to do is follow the basic steps as you go along.