• phaolo

    phaolo

    @phaolo

    Viewing 15 replies - 1 through 15 (of 59 total)
    Author
    Replies
    • in reply to: Printers can drive you insane #2569545

      I tried again after months and this time the setup didn’t hang without recognizing the printer, so maybe something changed with the driver or in Windows.

      Anyway, thanks for the suggestions.

    • in reply to: Printers can drive you insane #2535527

      I still haven’t managed to make Win10 recognize my old LaserJet Pro M1132 sadly (USB only).
      I tried changing cables, pc, drivers (even selecting basic ones), but nothing works.
      The computer doesn’t see it connected.

      P.s: it worked on the old Win7-8

    • About Win7, on the CVE-2020-0796 page there’s a FAQ that specifies:

      Are older versions of Windows (other than what is listed in the Security Updates table) affected by this vulnerability?

      No, the vulnerability exists in a new feature that was added to Windows 10 version 1903. Older versions of Windows do not support SMBv3.1.1 compression and are not affected.

      So we should be safe for this, at least 😛

    • I frankly expected that some trick like this would have been discovered, but I also knew that it would have been announced way too early, thus making it absolutely useless -_-‘

      1 user thanked author for this post.
    • in reply to: MS-DEFCON 4: Time to get the November patches installed #2015111

      “Win7 and 8.1 do not include telemetry this month”

      Good but.. would it make sense to install patch “pieces” every other month?
      Wouldn’t it cause a mess?
      For now I’m staying at May..

    • in reply to: Patching as a social responsibility #1979066

      Speaking of which, is MS still ruining the Security-Only patches for Win7 with telemetry?
      I stopped patching in May due to this..
      (and for the bugs, and for the fear of them sabotaging the old OS)

      1 user thanked author for this post.
    • I use Firefox since forever, but I checked the Defaults Programs page just for curiosity.
      It seems I still have IE associated with 3 files (.url, .website, .partial), but I can’t remove them, they’re greyed out..

      • This reply was modified 5 years, 5 months ago by phaolo.
    • in reply to: Startup programs not working anymore #1716402

      I’m not using an antivirus at the moment.
      Maybe it could be ZoneAlarm’s fault, but so far I haven’t been able to verify it.

      Btw the issue came back and strangely, it even persisted after restoring to previously-created points without it.

      So, I tried using  Msconfig to do a selective restart without any third-party service&program and the startup progs worked again. Then I re-enabled them one-by-one (actually in groups) to identify the culprit, until.. I basically ended up with the normal start.
      And the issue vanished again.. ¯\_(O_o)_/¯

      1 user thanked author for this post.
    • in reply to: Startup programs not working anymore #1652574

      Oh well.. I managed to restore via Safe Mode.
      This is still annoying and weird, but as long I can go back, I guess I’m ok..

      1 user thanked author for this post.
    • in reply to: May 2019 Patch Tuesday arrives #1630498

      Gosh.. fingers crossed. For now all looks normal.
      Btw why couldn’t we just run pciclearstalecache.exe manually?
      That’s what the patch does at the start, no?
      (also, why doesn’t it simply stop, if it cannot find the file?)

    • in reply to: May 2019 Patch Tuesday arrives #1629859

      Ouch.. I didn’t see any command prompt.

      Btw the file from the catalog was called (I didn’t remove the SHA1 tho..):
      pciclearstalecache_d243a607b50db10ed50f03cff570498018c61a59.exe

      Checking the registry, then, I noticed some errors.

      • Since years I use SoftwareRestrictionPolicies to limit cmd.exe to be used only with admin rights, due to the fear of ransomware.
        It never created problem with patches, but now I saw an entry about it:
        Access to C:\Windows\system32\cmd.exe has been restricted [..] 
      • Also:
        The winlogon notification subscriber <TrustedInstaller> is taking long time to handle the notification event (CreateSession).
        The winlogon notification subscriber <TrustedInstaller> failed a critical notification event.

      Is there a more detailed log somewhere?
      (I’ve found windowsupdate.log, but I can’t understand anything lol)

      Should I reinstall the patches? :\

      • This reply was modified 5 years, 9 months ago by phaolo.
    • in reply to: May 2019 Patch Tuesday arrives #1628952

      Yeah, I meant in the past, the first time pciclearstalecache.exe appeared.
      Anyway, I’ll follow those instructions now.

    • in reply to: May 2019 Patch Tuesday arrives #1628839

      Wait, it hadn’t to be run manually?
      The instructions for it were always changing..

      I executed it before and after installing the patch (I think it was 4099950).
      Did I screw up something? O_o

      (why isn’t this simply included in the package btw?)

    • I think I got those from the Asus site for my mobo. They surely caused a lot of issues.
      I’ll uninstall them if they’re even useless for me, thanks.

    • Sorry, I have to add one more thing to this thread (I wish to think that this mess could be useful to someone at some point):
      the real culprit was the “Link Power Management” setting enabled inside the “Intel Rapid Storage” program. It caused some (undetected by monitoring tools?) disk latency which affected everything else.

      2 users thanked author for this post.
    Viewing 15 replies - 1 through 15 (of 59 total)