yay ok brother I'm a guy a little nervous and decided so in a few minutes I'll be back using the newest version of Win10 21H1 that I downloaded this morning and then I must post the result and more on another usb stick I already have Linux mint also ready to install result: what is more stable is who live will see!
ok I know NTLite also is very good but after that I know my 2nd Master Chris Titus things are more simple to me altough works with Powershell is not one simple task...
All new updates: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-653#post-1689133
Updated the 1809 Updates Overview: https://forums.mydigitallife.net/th...-17763-xxx-pc-rs5.77945/page-216#post-1490183
hmm finally managed to solve the serious problem of pagefile.sys on my WinOS 10 LTSC 2019 after almost going crazy that I found the solution I found that simply was using the wrong iso 17.763.1 when the correct version is 17.763.316 hehe are bones of the officio I think... EDIT: hehe sometimes life plays tricks on people!!!, hmm this happened to me in this serious problem described above so this time I did not use the MSMG Toolkit or third party tools to modify the system so I used the CORRECT iso without changing anything for installation left the modifications to be made already with the system online using only the brain and my still small knowledge when it comes to subject but to be more brief I can say that this was my best build ever using only the native tools of Windows 10 and of course with the W10 ADK for W10 LTSC 2019 nothing more; then concluding I can say that the version of W10 easier to work is undoubtedly the version LTSC had no problems with the command sfc /scannow and in system configuration everything works as fast as it should be ... the system response is fantastic like I've never seen before is this.
Yes of course you can remove apps with PowerShell too but it's less intuitive and if you don't remove all apps a bit more annoying too.
No, I don't dual boot Windows/Linux. I just knew there was that way to use UTC in the firmware. Next best option would be to use an NTP client and correct the clock at bootup.
This is the solution that worked for me to make Linux use 'Local' time. At the command prompt enter: sudo timedatectl set-local-rtc 1
Nimbus2000, that command is exactly the one I used in linux, where I got a bold 'white text' warning asking me to turn the settings back to what they were because its not a good thing to force linux to use RTC time. And that is why I'm looking for a 'better' solution.
I force Windows to UTC, and since I install Linux after Windows, I also switch Linux over to UTC as well (the distros I use use localtime if it detects an existing Windows install). In Linux: Code: sudo timedatectl set-local-rtc '0' And Windows: Code: reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation" /v "RealTimeIsUniversal" /t REG_QWORD /d "1" /f Never had any issues in either OS that I'm aware of. I've used Ubuntu, Fedora, and openSUSE TW. I think my BIOS time stays localtime or something, but afaik that doesn't affect anything.
Not sure if it's just me but I don't see any threads on Windows 10 LTSC 2021 yet. Does anyone know when it's coming out yet? Any rumors or news links?
hello twizter well I have not anti-virus for years and for my safety I use Adguard premium is enough...
I am not sure why (or what distribution) would give that warning. All I can say is that I have used that command on numerous Debian based distros ever since Systemd came along (Debian, Ubuntu, Mint, etc). I have never seen a warning or experienced a problem. As we are straying off topic, it may be time to move to the Linux thread.