Windows 10 Redstone 5

Discussion in 'Windows OS and Software' started by Ultra Male, Sep 25, 2018.

  1. Vasudev

    Vasudev Notebook Nobel Laureate

    Reputations:
    7,138
    Messages:
    10,314
    Likes Received:
    7,582
    Trophy Points:
    931
    Yeah scan only changed files aka whitelist is a lifesaver. BD free is buggy, I recently got a 6 month full version of BD TS 2019 and it was buggy; it blocked WU,blocked apps even with whitelist, blocked itself from updating defs and UI etc... Threw it out and switch to kaspersky free for peace of mind.
     
    6.|THE|1|BOSS|.9 likes this.
  2. 6.|THE|1|BOSS|.9

    6.|THE|1|BOSS|.9 Notebook Evangelist

    Reputations:
    887
    Messages:
    491
    Likes Received:
    962
    Trophy Points:
    106
    Or Just don't use any antivirus... like me :rolleyes: if any virus came to me... I face it by myself although it only happened 2~3 times since 3 years ago... and I always won :D

    [THEBOSS 3 - 0 Viruses or Malware] :cool:
     
  3. Vasudev

    Vasudev Notebook Nobel Laureate

    Reputations:
    7,138
    Messages:
    10,314
    Likes Received:
    7,582
    Trophy Points:
    931
    I never use Windows 7/8.1/10 w/o an AV. On Linux no AV at all! If there was any virus I'd just use kaspersky rescue disk to disinfect the PC or even use Linux to quickly delete all AV references and shortcuts.
     
    6.|THE|1|BOSS|.9 likes this.
  4. heliada

    heliada Notebook Evangelist

    Reputations:
    259
    Messages:
    585
    Likes Received:
    502
    Trophy Points:
    106
    I don't think that is smart on windows... There are plenty of viruses that act undercover, collecting your data etc (gl if you use some important passwords or do your banking in that time). You might never know something sneaked its way in no matter how careful you are. And lets admit it, the majority of pc users aren't even all that careful. Even I admit that I thought my first laptop was virus free until I ran some malwarebytes and avast pre-boot scans on it... but it turns out it did not help the issue as the thing was just overheating despite going twice for warranty for shutting down. I knew nothing about laptops/pc's back then at all, my windows 7 got so bloated it took ages to boot and probably like 10 seconds to even open windows explorer. When the bf opened the laptop up back in 2013, he encountered melted plastic and rock solid paste and the poor laptop was just barely out of warranty at the time, but well.. gaming on integrated graphics was never a good idea to begin with.
     
    Robbo99999 and 6.|THE|1|BOSS|.9 like this.
  5. 6.|THE|1|BOSS|.9

    6.|THE|1|BOSS|.9 Notebook Evangelist

    Reputations:
    887
    Messages:
    491
    Likes Received:
    962
    Trophy Points:
    106
    3 years with the same performance and temperature.. without any hiccups :D but I agree with you that this post applies for people who doesn't know what they are doing... :) but I know what I am doing... especially 3 years of usage with the most important scenario... banking and payment and my job, etc...


    You don't need an automated stupid bot to protect you from infection or security breach... I don't believe on Antivirus... I believe on human knowledge & with knowledge... you don't need any useless (the so called Antivirus) to protect you :D
     
    Vasudev likes this.
  6. Vasudev

    Vasudev Notebook Nobel Laureate

    Reputations:
    7,138
    Messages:
    10,314
    Likes Received:
    7,582
    Trophy Points:
    931
    I prefer pairing with WD or Kaspersky just like GTA 5 Armour that gets basic protection. You should use linux for everything and WINE is pretty good and Win 10 is used for BIOS mods and few others....
     
    6.|THE|1|BOSS|.9 likes this.
  7. Papusan

    Papusan JOKEBOOK's Sucks! Dont waste your $$$ on FILTHY

    Reputations:
    22,603
    Messages:
    23,571
    Likes Received:
    40,875
    Trophy Points:
    931
    May 1, 2019—KB4501835 (OS Build 17763.439)

    Improvements and fixes

    This update includes quality improvements. Key changes include:
    • Addresses an issue that prevents the CALDATETIME structure from handling more than four Japanese Eras. For more information, see KB4469068.
    • Updates the NLS registry to support the new Japanese Era. For more information, see KB4469068.
    • Addresses an issue that causes the DateTimePicker to display the date incorrectly in the Japanese date format. For more information, see KB4469068.
    • Addresses an issue that causes the Date and Time Settings control to cache old Eras and prevents the control from refreshing when the time enters the new Japanese Era. For more information, see KB4469068.
    • Updates fonts to support the new Japanese Era. For more information, see KB4469068.
    • Addresses an issue that prevents an input method editor (IME) from supporting the new Japanese Era character. For more information, see KB4469068.
    • Addresses an issue that causes the Clock and Calendar flyout control to display the day of the week incorrectly mapped to a date in the month of the new Japanese Era. For more information, see KB4469068.
    • Adds alternative fonts for the new Japanese Era fonts. For more information, see KB4469068.
    • Enables Text-To-Speech (TTS) functionality to support new Japanese Era characters. For more information, see KB4469068.
    • Addresses an issue in Unified Write Filter (UWF) that prevents Hibernate Once/Resume Many (HORM) from working as expected on Unified Extensible Firmware Interface (UEFI) systems.

    Download link:
    KB4501835 (OS Build 17763.439)
     
  8. heliada

    heliada Notebook Evangelist

    Reputations:
    259
    Messages:
    585
    Likes Received:
    502
    Trophy Points:
    106
    Just a little update on my downclocking issue: resetting power schemes seems to have been a temporary fix. It now either no longer works or the issue comes back randomly at reboot. Seeing I don't feel like reinstalling I removed the latest update (KB4493509) and will see what happens. Next step would be to check all PSU cables (especially cpu one) - sadly the case needs to come apart quite a lot for that as my giant noctua cooler does not allow easy access.... thank god the top can be removed lol. Then I guess updating the bios as I am on the one the mb originally shipped with ><. Anyway just letting you all know the issue is still present. It would do me a great favor if you are on OS build 17763.1 w10 pro if you could pick high performance mode and let hwinfo let in the background for about 20 mins while normally using the pc/laptop. If you see any unwelcome 800MHz I'd love to hear it :D

    PS. mmm seems new chipset drivers are out since 3 days. Just installed, will be observing.
     
    Last edited: May 2, 2019
    6.|THE|1|BOSS|.9 and Vasudev like this.
  9. epguy3

    epguy3 Notebook Consultant

    Reputations:
    117
    Messages:
    220
    Likes Received:
    119
    Trophy Points:
    56
    the KB4501835 update is rendered moot now as Microsoft has just released a newer update for 1809 and contains more new non-security fixes

    KB4495667 (build 17763.475) (released May 3)

    https://www.catalog.update.microsoft.com/Search.aspx?q=4495667

    did you get a chance to install the KB4465065 microcode update for 1809, heliada?
     
    6.|THE|1|BOSS|.9, Papusan and Vasudev like this.
  10. Papusan

    Papusan JOKEBOOK's Sucks! Dont waste your $$$ on FILTHY

    Reputations:
    22,603
    Messages:
    23,571
    Likes Received:
    40,875
    Trophy Points:
    931
    And with a bunch of fixes. I wonder why the Redmond Retards didn't dare push those out 1. May with Build 17763.439:rolleyes:

    What's new in Windows 10 Build 17763.475
    • Allows the built-in Administrator account to run Microsoft Office setup after downloading the installer in Microsoft Edge.
    • Addresses an issue that causes Internet Explorer Automation to fail in certain instances.
    • Addresses an issue that may prevent Custom URI Schemes for Application Protocol handlers from starting the corresponding application for local intranet and trusted sites on Internet Explorer.
    • Addresses an issue that prevents certain apps from launching when you set folder redirection for the Roaming AppData folder to a network path.
    • Addresses an issue in Gdi32full.dll that causes an application to stop responding.
    • Addresses an issue that may cause the UI to stop responding for several seconds when scrolling in windows that have many child windows.
    • Addresses an issue that may cause a touch screen to stop working after restart.
    • Enables a touch keyboard to support new Japanese Era characters. For more information, see KB4469068.
    • Addresses an issue that causes ShellExperienceHost.exe to stop working when the start date for the Japanese Era is not on the first day of the month. For more information, see KB4469068.
    • Addresses an issue that prevents the CALDATETIME structure from handling more than four Japanese Eras. For more information, see KB4469068.
    • Updates the NLS registry to support the new Japanese Era. For more information, see KB4469068.
    • Addresses an issue that causes the DateTimePicker to display the date incorrectly in the Japanese date format. For more information, see KB4469068.
    • Addresses an issue that causes the Date and Time Settings control to cache old Eras and prevents the control from refreshing when the time enters the new Japanese Era. For more information, see KB4469068.
    • Updates fonts to support the new Japanese Era. For more information, see KB4469068.
    • Addresses an issue that prevents an input method editor (IME) from supporting the new Japanese Era character. For more information, see KB4469068.
    • Addresses an issue that causes the Clock and Calendar flyout control to display the day of the week incorrectly mapped to a date in the month of the new Japanese Era. For more information, see KB4469068.
    • Adds alternative fonts for the new Japanese Era fonts. For more information, see KB4469068.
    • Enables Text-To-Speech (TTS) functionality to support new Japanese Era characters. For more information, see KB4469068.
    • Allows existing devices that are managed by Configuration Manager to be enrolled in Microsoft Intune using Co-management without any user interaction. It does not require an active user to be logged in, and there are no Multi Factor Authentication (MFA) prompts. This update also allows the Co-managed mobile device management (MDM) enrollment to use the device credential it received when the device is enabled to join Hybrid Azure Active Directory (AADJ).
    • Improves access to detailed troubleshooting and diagnostic logs from managed devices, such as business PCs, when using a PC cloud management service. PC cloud management services include Microsoft Intune or other Mobile Device Management (MDM) providers for Windows.
    • Addresses an issue that may allow a user to continue logging on to an account using a smart card after disabling the account.
    • Addresses an issue that prevents access to enterprise resources when using Kerberos with Windows Hello for Business (WHfB) credentials. This causes users to receive multiple prompts to provide their credentials.
    • Addresses an issue that occasionally causes a PostScript printer to use the wrong font.
    • Addresses an issue that causes Lightweight Directory Access Protocol (LDAP) client applications to stop responding for at least 30 seconds when many LDAP queries are requested through multiple connections. This occurs because of a race condition in wldap32.dll. You must install this update on the LDAP client that calls wldap32.dll.
    • Addresses an issue that causes a roaming profile user to lose customized Start menu settings after upgrading the operating system (OS). After installing this update, administrators must enable the UseProfilePathMinorExtensionVersion registry setting described in KB4493782 for roaming user profiles (RUP). This key allows you to create a new RUP for an upgraded OS and prevents the loss of a custom Start menu. The RUP must be stored locally, and you must restart the device to enable the feature.
    • Addresses an issue that causes connection requests to the Remote Desktop Session Host (RDSH) servers in the deployment to fail. This issue occurs because of a deadlock in the Connection Broker.
    • Addresses an issue that may prevent Cluster Aware Update from restarting nodes when a cluster's credentials are reset. Cluster Aware Update must restart nodes after installing an update. The error is the following:
    SAVED BY THEIR SECURE browser, Internet Explorer:oops:
    upload_2019-5-3_22-13-35.png
     
    Vasudev and 6.|THE|1|BOSS|.9 like this.
Loading...

Share This Page