jmonroe0914

If the pagefile isn't being used, it's because it's been disabled by Samsung Magician. The pagefile serves an extremely important service and should be set to a minimum of 16GB [at least equivalent to the amount of RAM installed, since it's there for RAM usage]. The 840 Pro carries a 5 year warranty, so writes shouldn't be of much importance. I frequently use 10 - 11GB page file sizes with Windows 10, and if you're using a high quality SSD, you'll notice a more responsive system over time by ensuring it has at least 16GB allocated to the pagefile (to understand why, do some reading on google to understand what the pagefile is, why it's there, and how it affects system performance). I utilize Hyper-V quite frequently. so my pagefile is set to the same size as my RAM [32GB] on my 850 Evo, and has been known to climb above 20GB of usage. Either allowing windows to manage the size, or setting a minimum 1024mb / maximum 16384MB would be best. RAM transfers occur at 2GB/s+, whereas PageFile transfers on HDDs occur at a max of 160MB/s [generally far less, < ~100MB/s; whereas the 840 Pro transfers at 520MB/s, probably not dipping below 400MB/s for pagefile read/writes

Not sure how something that's free is overpriced...

I don't post information I haven't personally experienced and verified myself. The things I described happened to my system. And not because of anything I've done wrong. It's not venting and it's not made up when it actually happens. It's FACT, pal. You need to understand that you're conversing with people who may just know more than you do about Windows. Don't look now but reinstalling and re-enabling cloud software that's been removed - e.g., OneDrive - that actively seeks to transfer your data to online servers is far more an attempt to breech privacy than "accidentally" reverting a few settings. If you think Microsoft reverted those privacy settings by accident then you're quite possibly deluded. They know exactly what they're doing and they continually test the waters to see what they can get away with. Their mission is redefine what people will accept. Your sig implies you're aware that social / peer pressure changes people's opinions, yet somehow you can't (or refuse to) see the reality of what's going on yourself. -Noel Instead of being rude and hostile, perhaps you could re-read my post I never stated the things you said didn't happen (in fact, I acknowledged they did...)I never said end users did anything wrong (how you formulated this inference is most perplexing...)It was you who stated "or any of the other things people have seen and documented" which is different than saying it happened to you.It doesn't help anyone when an end user with a vendetta against something or some corporation rants about it in multiple posts... even more importantly, it does the direct opposite, thereby a disservice, to what you're intending for it to do. It turns people off and causes them to dismiss what you've written, regardless of how relevant it may be, as that of a raving, ranting, cantankerous senior who's irritable about the slightest of changes and evolutions the world makes around them. What opinion you, I, or any other user has about this simply doesn't matter and is of no consequence. Microsoft blatantly stated, in an extremely specific statement, exactly why the update was pulled mere hours after being pushed to Windows Update. There are plenty of sites that cater to nonsensical conspiracy theories... this is not one of them.

If you're referring to Windows setting your user name, specifically your user folder, to the first few digits of your email, the way to avoid this is to first create a local account with the user name you want, then once logged into it, choose to convert it to an email login. User folder name stays the same, and your user name for permissions can either be entered as the original local user name or the email address.

Windows Core versions are single language only versions, meaning language packs cannot be downloaded for them and are locked to one language only. Windows core and Window IoT Core are not the same, and Server Core isn't even in the same ballpark (server OSes cannot generally run on PC motherboards, just as server boards can generally not run desktop OSes - Server OSes are not remotely similar to desktop OSes) . Windows Core versions are desktop OSes, IoT Core versions are a competitor of Raspberry Pi. With Windows 10, all versions, except IoT core, are literally the same OS. Windows 10 Phone will obviously be slimmed down version of Home or Pro; however, whether it's Windows Phone, Xbox One, or a PC, it's the exact same OS. All that differs are the features offered.

Due to the level of complexity of the original control panel, coupled with it's heavy usage and integration into the Settings App, speaks for itself it's not going away. I'm not sure how the journalist who wrote the article inferred what they did, as Mr. Aul never stated anything to the effect of the original control panel is being killed off "Having two separate implementations means more code complexity and disk/mem usage. Getting to one is leaner"The Settings app will continue to be used as the main control panel area, with more complex actions handed off to the original control panel, the same way the Settings app currently operates, and has operated, since it's inception in Windows 8. While Microsoft's goal is leaner, and less complex, coding, the reality is there is simply no efficient way to incorporate the original control panel into something new. It's the equivalent of trying to reinvent the wheel... there's a reason why there hasn't been a single innovation applied to the wheel in more than 5,500 years. On top of that, you then must ask the question "If not the original control panel, then what?". There's no efficient, nor probable, way to incorporate the complexity of the original control panel into the Settings App. Take the Windows Firewall (which I've never used, but it a perfect example of the type of complexity)... anyone care to fathom how that's supposed to be apart of the Settings App? What about Programs and Features? Anyone who can intelligently explain how the Settings App's System -> Apps & Features would make things less complex, I'd be interested in hearing from that perspective. The Settings app is made for touch devices, whether it be laptops, tablets, or desktop monitors... it is not intended, nor built in such a way, to be replacement of the original Control Panel. It really comes down to Occam's Razor - Microsoft has had 5+ years to attempt to incorporate the original Control Panel into the Settings Apps... there's a reason this has yet to occur.

Out of curiosity, how small of a size are you going for? Using an install.esd over an install.wim will save you ~1GB of space, and considering the unpacked install.wim/esd is ~19GB, that's a fairly substantial compression ratio.

I ran aero glass on Windows 8 prior to WindowBlinds 8 being released, and due to the GUI glitches that occurred then, and probably still occur now, I personally recommend you wait a few months for WindowBlinds 10 to be released. Anyone looking for transparency cares about how their GUI looks, and WindowBlinds does that and so much more without having GUI glitches. AeroGlass works, don't get me wrong, but it's quick and dirty instead of the right, and extremely complex, way it should be done. DWM has extremely deep hooks within Windows and is not the easiest to bypass, which is the main reason it takes several months following a new Windows release for a compatible version of WindowBlinds to be released. Without AeroGlass you can get a fully transparent taskbar with Start10 from Stardock (who also makes WindowBlinds). This may be possible natively on Win 10, however I can't remember.

First, it's not recommended to utilize Windows Defender... use it and it's not a matter of if, but when, your system will be compromised. Is this iteration [in Windows 10] far better than previous versions? Absolutely... but is it anywhere near good enough to utilize and be confident it will prevent malicious code, not at all. Utilize a top rated internet security solution that offers stateful antivirus, HIPS [antimalware], sandboxing, and firewall. I'm partial to Comodo Internet Security Pro, but choose what you like, provided whatever you choose has a rating above 98% and scores in the top 5. Once a 3rd party internet security solution or standalone antivirus is installed, Windows Defender automatically disables itself and prevents itself from being accessed. I've never seen the error you're getting, as it's not a normal error and implies the wrong architecture of some system files were installed, which is not possible to be done via the Windows installer. You can try repairing the component store (WinSxS), rebooting, then running SFC, and rebooting again. Both commands must be run from an admin terminal (command or powershell) and reboots must occur in between running both. 1st, ensure no component store corruption exists dism /online /cleanup-image /restorehealth2nd, ensure no system file corruption exists sfc /scannow

I am a bit perplexed about something... the BCD store shouldn't control what's being shown during POST, as it has no bearing on POST. I could very well be wrong, however my understanding is the BCD store doesn't come into play until after the BIOS/UEFI Firmware hands off to the installed bootloader. Pressing F12, F2, or any BIOS/UEFI Firmware hotkey interrupts the boot process; hence the firmware never actually gets to the process of handing off the boot process to the installed bootloader. For example, pressing F12 with no HDD or OS installed will still provide a boot menu with options to choose from, Enter Setup usually be the last one, if not the onboard DOS diagnostics. Have you tried re-flashing the BIOS/UEFI firmware? On the off chance my understanding of the BCD store is wrong: Have you tried bootrec? Boot into WinRE/WinPE: bootrec /fixboot bootrec /rebuildbcd Beyond adding custom entries to BCD, I've never worked with it beyond that. If you know the GUID for BIOS Setup entry, you should be able to re-add it via the command line or a program like Boot Ice (an extremely handy and powerful little program).

I need my boots for this... ****, that smells bad. So being called out on reverting peoples' settings resulted in their blocking an update then re-issuing it with a promise to restore settings real soon now... That implies they HAVE a copy of the previous settings somewhere. And really? Only THOSE four settings? Puhleeease, there were more than that. There's not even a mention of the fact that all removed Apps are reinstalled, disabled services are re-enabled, disabled scheduled tasks are re-enabled, System Restore is turned off, or any of the other things people have seen and documented. Everything any more seems like just a test to see how much people will put up with. Only when lawyers hit them do they bend, and even then, just as little as possible. We need to stop putting up with their crap, even a little bit of it! If you're on Win 10, it's time to seriously consider reverting back to your prior OS and sending Microsoft the message that this s*** won't fly! -Noel build 1511 was pulled due to an update contained therein that inadvertently caused privacy settings to be reset to default, allowing third parties access to the end user's personal information even if the end user had previously chosen to deny access. I would encourage all to ensure they have a clear understanding of the facts prior to venting... venting about what exactly, I'm not sure. Would you rather have had them leave it as it was and had your privacy settings reset without knowing they had been? (It was also only pulled for a short period of time) The vast majority of user issues with Windows 10 are due to the end user's environment, having nothing to do with Windows 10 itself. Each is welcome to their own opinion and differing opinions should always be welcomed, however it doesn't help anyone when misinformation and hyperbole are given heavier weight than facts. I've yet to come across a thread or post regarding: "...all removed Apps are re-installed, disabled services are re-enabled, disabled scheduled tasks are re-enabled, System Restore is turned off, or any of the other things people have seen and documented." However, if you have, a likely cause could be from joining or removing oneself from the Insider's program (which performs a reinstall of Windows both times, by means of an in place upgrade), of which would reset certain things depending if they were part of files that were reinstalled. Using a Microsoft account to sign in would alleviate many settings changes, since many custom settings are restored from OneDrive (provided you have syncing turned on, which it should be). In regards to the... venting... for lack of a better word, no one's forcing anyone to upgrade to Windows 10. If a person doesn't wish to utilize it, then don't... don't take the free upgrade, stick to Windows 7 until 2022 and then pay for a Windows 10 license. If Windows 10 truly had all the problems described in this thread and others, they would be reproducible on any machine running it... but they're not. I've been reading the same rhetoric for months, yet not once have I come across a thread about a critical bug a user claims is due to Windows 10 and been able to reproduce it... not once (with the exception of a minor bug preventing the installation of TCP/IP services - the same or similar bug popped up, and was subsequently fixed, prior to Windows' 10 RTM). Obviously these users aren't making up the issues they're having, leaving the only probability being the issues are due to the user environment, not Windows 10 itself (environment is classified as the motherboard, anything physically attached to it, 3rd party drivers, and 3rd party software). The bulk of all Windows 10 issues come down to three things... not clean installing, not following the proper steps if clean installed, and improper/incompatible drivers and software.

I'm going to assume you have AMD graphics? You're getting the error due to a parity mismatch with opencl.dll 015-11-27 10:37:31,InfoCSI 00003a70Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :Found: {l:32 15Zo6QE4AUfojzxIYHfgI35HXL9fri8ouLdmre4jJQc=}Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=} 2015-11-27 10:37:31InfoCSI00003a71[sR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corruptedThis is a long standing issue with AMD graphics drivers and is simple to fix... You need to apply the install.wim of the install media to a folder and use that folder's Windows directory as the source for the DISM repair (mounting the install.wim will not allow for the correct cab to be pulled for some reason, nor will specifying the source as the WIM/ESD) Prior to running the commands below, download the most recent driver from AMD's site and install it. Reboot afterwards, then proceed below. I would save the batch below, as you will more than likely have to perform this after every graphics driver updateApply the Install.wim (install media root -> Sources\Install.wim) to C:\Temp.Copy the commands below to a text file, rename the file extension to .bat, right click, select Run as Administrator. C:\ = System Partition D:\ = path to install.wim C:\Temp = Install.wim apply directory mkdir C:\Temp DISM /apply-image /imagefile:D:\Sources\Install.wim /index:1 /applydir:C:\Temp DISM /online /cleanup-image /restorehealth /source:C:\Temp\Windows pause rmdir /s /q C:\Temp pause The first pause is there to allow you to verify the component repair finished successfully... if it did not, close the command window, which will terminate the batch file. Determine why it failed via the dism and cbs log, then re-run starting with the cleanup-image command. You will more than likely receive an error after the rmdir command due to denied access to bootmgr... close out the command window, select C:\Temp in Explorer and delete it (it should delete without issue). Failing to delete this prior to rebooting can cause an OS selection menu to pop up prior to booting Windows.

Nice little tool for what it does. I prefer RegEditX's RegCrawler search function, but that's just personal preference. While I see the appeal of opening the registry automatically when a key is copied to the clipboard, I'm perplexed at why one wouldn't simply paste the reg key path into regedit, which automatically goes to whatever is pasted.

In regards to *nix OSes, I can appreciate where you're coming from and trying to propose a helpful option to users, however *nix Oses and windows permissions are nothing alike. *nix OSes have always been better at managing permissions than Windows - for example, you can deny r/w privileges on *nix OSes, but still grant the user execute privileges... this cannot be done on Windows, as the equivalent on Windows would be read, write, and modify. Going out of the way to start applications as a different user (other than admin) creates far more problems than it solves, most significantly it's a massive inconvenience since every day actions create an approval request, from utilizing the control panel, running command line tools such as DISM, to a myriad of other every day uses having nothing to do with internet downloads. A far better and much more effective means is to educate oneself with basic IT security practices: dutifully setting up a quality Internet Security program that offers stateful antivirus, HIPS protection, as well as a sandbox and a stateful firewall.Windows' Firewall is a great firewall, but not in it's default state. If one takes the 3 or so days to set it up properly and dump most of the the default rules, then it's a superb firewall... but only if it's customized and most of the default rules junkedIn combination, a stateful firewall, such as iptables, running on a WAN facing router with UPnP disabled and WiFi encryption set to WPA2 (AES/CCMP, not TKIP)I personally don't recommend buying consumer routers that do not have OpenWRT (preferably) or DD-WRT support.If one is truly wanting security, building your own router and running a UTM [unified Threat Management] OS, which incorporates a firewall, antivirus,antimalware, and endpoint security all rolled into one. You can build a high quality router for under $300 (the same cost as a top of the line consumer router) and run Sophos UTM, PFsense, or a few others for free (as long as it's used for home use and not business use). Provided you buy a server board with a mini-pcie slot, you can also use it as an ac wifi access point.Running router OSes has a slight learning curve and should not be done unless one is willing to spend some time troubleshooting if a problem arises.Not utilizing public WiFi without a separate firewall profile setup to only allow outbound traffic on select ports (53, 80, 123, & 443 should be all that will be required for normal browsing), blocking all other traffic in and out of the PC.NETBios set to disabled under each network interfaceBlocking the following within the PC firewall:Inbound/Outbound TCP/UDP on 4444 (never allow traffic on this port period... there exists more exploits that use this port than legitimate assigned uses)Inbound ICMP message types: 3 (Destination Unreachable), 8 (Echo Request), 13 (Timestamp), 15 (Information Request), and 17 (Address Mark Request)Inbound/Outbound TCP/UDP traffic on ports 137, 138, 139, & 445 (unless utilizing network/CIFS shares, at which point rules should be added to the applications needing access to those ports for CIFS shares, with the global rule being drop (or deny/block)Inbound/Outbound TCP/UDP on 22 (SSH), 23 (TelNet), & 1194 (OpenVPN) Default ports for these services should never be usedlearning what programs should and should not need admin accessSandboxing download folders with virtual access only, removing files only once they've been scanned by an antivirus/antimalware [HIPS] programNot downloading programs from sites unless it's the developer's siteNot downloading games, unless they're from trusted developers, and only opening them after you've verified the digital certificate to make sure it's signed by a trusted CA and has not been tampered with.Verifying hashes of all programs downloaded prior to running/installing. If the hashes don't match, do not open them. Try redownloading it once more, and if the same occurs, alert the developer and check back later.There's plenty more, but they're all common sense, basic IT security practices that anyone owning a device that connects to the internet should know.

As others have mentioned, if you're going to take the time to make a recovery disk, you might as well simply wim the entire partition. It should take roughly the same amount of time, and depending on the size of your ssd, you may even be able to replace whatever is on the recovery drive with the wim you created (using maximum compression). It takes ~75 min/per 100GB on my system using maximum compression for a total of ~ 4 hrs to WIM ~ 350GB data on my system partition. If you're interested, this is a great tutorial on creating your own custom WinPE/RE image: http://reboot.pro/topic/19156-create-a-bootable-winpe-50-x64-usb-drive/ DISM Capture Command: dism /Capture-Image /ImageFile:E:\Recovery\Windows81x64_Base.wim /CaptureDir:C:\ /Name:"Windows81x64_Base" /compress:max /norpfix /checkintegrity /verify /scratchdir:D:\scratchThe scratch directory is vital as WinPE/RE only has a couple of hundred MB set aside for scratch, and it will fail if it runs out of scratch. I generally point it to my second internal hdd, however if you're using an external drive to save the image, you can also set that for scratch. I usually create a folder named scratch because there's tens of temp files that are created. CheckIntegrity and Verify both add significant time to the capture and restore process, and you can get away with not using them (though it's best practice to use them and is why it takes ~75mins/per 100GB for me). DISM Apply command: dism /Apply-Image /ImageFile:E:\Recovery\Windows81x64_Base.wim /index:1 /ApplyDir:C:\ /checkintegrity /verify /scratchdir:D:\scratch

Hmmm, never heard about that. Well, you never know. As a matter of fact the WIMBOOT (or WOF driver) is something that has been added in Windows 8.1, basically it is a "simple" enough approach, it is a kernel driver that can interpret a .wim file as if it was already an applied volume, so it does not in itself constitute anything particularly "complex" to deal with. But we are still in the earlier misunderstanding. Microsoft advocates the use of a "recovery environment" which is based on a "normal" .wim, the WinRE.wim, starting from Vista, the situation AFAIK is/was the following: with Vista the method was recommended but very few OEM used itwith 7 it was strongly recommended and a few OEM's ditched their own "custom" recovery environment and adopted the MS waystarting with 8 the "recovery environment" became mandatorystill they are two different things, one is the "recovery environment" (which is a kind of "built-in PE") and one is the "recovery partition" or the "recovery media" that you can create on DVD(s) or on a USB stick. What is now compulsory is the presence of the WinRE, the OEM is free to use the Recovery Environment to apply/restore the mass storage device to "factory state" but remains free to use a completely different, custom, approach to obtain the same. A number of low-cost/small SSD sized tablets may use Wimboot lately as the advantage it has is that the senseless amount of bloat a Windows install represents is strongly reduced due to the WIM format compression, though this only works initially as each and every subsequent update is going to be stored "flat" on the device (and it seems like the functionality will be removed in Windows 10), see: http://www.msfn.org/board/topic/173786-whats-up-with-the-bevy-of-optional-windows-81-updates/ From the contents of the USB drive you have, it does seem like a "normal" install/recovery, probably aimed to be saved on both DVD's and USB stick, if you check the size of the .swm's they should be compatible with DVD sizes, the presence of the reagent.xml file is "standard MS", while $PBR_DiskPart and $PBR_ResetConfig are "non-standard" AFAIK. So it is possible that the USB stick you have is a "mixed mode" making use partially of the MS approach and partially on some OEM customizations, the presence of the reagent.xml file implies the use of a WinRE.wim that seemingly you do not have, maybe from it's contents one could try to understand what has "gone wrong": http://www.terabyteunlimited.com/kb/article.php?id=587 jaclaz Couldn't one take a wim of the system, say after 1 month of updates, and replace the wimboot wim with the new image? I'm not sure if that would be possible or not, as I only just learned about the wimboot option within the past month and thought it was a horrible idea (great concept, horrible idea)... tablets are already slow enough, and even with an ssd it's still going to take a significant performance hit because of wimboot. Then again, I'm probably in the minority, as I've gotten extremely used to the fast performance of my M18x.

I've used WinBuilder (Win8.1SE v82) to build a custom PE/RE multiboot USB and I've added 4 ISOs to it and installed grub4dos (tried with bootice as well as RMPrepUSB), however I cannot get certain ISOs to boot as they hang at: (hd0,0) FAT12 BPB found with 0xEB (jmp) leading the boot sector. probed C/H/S = 80/2/18, probed total sectors = 2880 I've searched for hours on Google, however I can't find anything that references the cause of this. I'm getting this error with a custom repair iso, and gparted (most recent amd64) is hanging, eventually kicking back to bootloader command line after ~5min or so. PartedMagic (most recent from 2015.05.04) boots fine, as does the Comodo Rescue ISO. The Win8.1SE build is setup to boot to BCD with an option for Win8.1SE, WinRE, and grub4dos. Grub4dos then has several entries, 4 of which are ISOs added during the build. All menu.lst entries are mapped to (hd32), which would be right for a CD and I was curious if this would be the cause of the issue since it's a flash drive. I've tried partitioning the flash drive every which way, both through Win8.1SE and RMPrepUSB, but I can't seem to get gparted and the custom recovery iso, which contains both dos and linux utilities, to boot.