A user mentions moving towards Type 4 drivers in part because of a separate, unspecified issue with Lexmark's Type 3 universal driver.

{
  "signal_id": "3d349b85-2631-5b13-a7ec-89bd3db92ec7",
  "signal_type": "reddit-company",
  "signal_subtype": "customerFeedback",
  "detected_at": "2026-09-09T14:22:05+00:00",
  "company": {
    "name": "Lexmark",
    "domain": "lexmark.com"
  },
  "data": {
    "nsfw": false,
    "stage": "none",
    "awards": 0,
    "timing": "ongoing_state",
    "topics": [
      "printing",
      "drivers"
    ],
    "post_id": "1wbmztl",
    "summary": "A user mentions moving towards Type 4 drivers in part because of a separate, unspecified issue with Lexmark's Type 3 universal driver.",
    "category": "reliability",
    "comments": [
      {
        "url": "https://www.reddit.com/r/WindowsServer/comments/1wbmztl/comment/p8rypc6/",
        "depth": 0,
        "score": 3,
        "author": "OinkyConfidence",
        "excerpt": "Man, I really WANT to love v4 printer drivers, but v3's just seem so much better. Designed for each printer, not universal. But they're kernel-level, and MS wants to kill them off, sadly. Hopefully the printer OEMs will get better at making drivers too.",
        "posted_at": "2026-09-09T16:40:49.000Z",
        "author_url": "https://www.reddit.com/user/OinkyConfidence/"
      },
      {
        "url": "https://www.reddit.com/r/WindowsServer/comments/1wbmztl/comment/p8vy21c/",
        "depth": 0,
        "score": 2,
        "author": "chandleya",
        "excerpt": "Sounds like an excellent case for Server 2022. Never in my life have I wanted to be on n for RDS. At least n-1.",
        "posted_at": "2026-09-10T04:05:43.000Z",
        "author_url": "https://www.reddit.com/user/chandleya/"
      },
      {
        "url": "https://www.reddit.com/r/WindowsServer/comments/1wbmztl/comment/p8seg8t/",
        "depth": 0,
        "score": 2,
        "author": "Excellent_Milk_3110",
        "excerpt": "I just install them on the rds itself and be done with it. Still occasionally something gets bugged but not as much as with shared printers.",
        "posted_at": "2026-09-09T17:47:42.000Z",
        "author_url": "https://www.reddit.com/user/Excellent_Milk_3110/"
      },
      {
        "url": "https://www.reddit.com/r/WindowsServer/comments/1wbmztl/comment/p8s5wo9/",
        "depth": 0,
        "score": 2,
        "author": "Bourne069",
        "excerpt": "Everytime I configured RDS and Printer Deployement I forced via GPO to disable printer driver updates for this exact reason. Something breaks literally everytime.",
        "posted_at": "2026-09-09T17:11:10.000Z",
        "author_url": "https://www.reddit.com/user/Bourne069/"
      },
      {
        "url": "https://www.reddit.com/r/WindowsServer/comments/1wbmztl/comment/p90dj3u/",
        "depth": 0,
        "score": 1,
        "author": "BlackV",
        "excerpt": "I saw this\n\n https://www.theregister.com/os-platforms/2026/08/25/microsoft-breaks-wpf-printing-with-net-update/5292116\n\n Maybe related",
        "posted_at": "2026-09-10T19:11:24.000Z",
        "author_url": "https://www.reddit.com/user/BlackV/"
      }
    ],
    "evidence": [
      "[post] The whole reason I am moving toward Type 4 in the first place is because of a completely separate issue I have with the Lexmark Type 3 driver."
    ],
    "virality": "somewhat_high",
    "post_date": "2026-09-09T14:22:05.000Z",
    "post_kind": "text",
    "post_text": "Initial reddit post:\n\nPSA: Windows Server 2025, RDS and Printer - TYPE 4 might break throught latest security update : r/WindowsServer\n\nHello guys, I need to vent and rant about it. For f*cks sake. This is a follow-up to my previous post about Windows Server 2025, RDS and Type 4 printer drivers. And at this point I seriously have a hard time believing this is just coincidence.\n\nAfter the previous printing issues, I went pretty much nuclear and built a completely new Windows Server 2025 RDS / FSLogix farm from scratch.\n\nNo in-place upgrades, no ancient RDS baggage, no mystery leftovers from old servers. Fresh servers, fresh configuration, fresh profiles.\n\nThe new farm was initially running build 26100.33296, based on our patch level from around August 26/28.\n\nAnd printing worked. Not \"mostly worked\". It just worked.\n\nThe whole new farm felt ridiculously good. Fast logons, clean FSLogix setup, no weird printer drama, everything finally felt like I had gotten rid of years of accumulated Windows/RDS nonsense.\n\nThen the servers moved to: 26100.33438\n\nAnd now printing is screwed again.\n\nOur print server itself has not been redesigned in between. The same shared queues and drivers are still there.\n\nWe currently have both Type 3 and Type 4 drivers in use:\n\nType 3\n\nLexmark Universal v2 XL\n\nKONICA MINOLTA Universal PCL\n\nType 4\n\nLexmark Universal v4 XL\n\nKONICA MINOLTA Universal V4...",
    "sentiment": "negative",
    "subreddit": "WindowsServer",
    "post_flair": [
      "Technical Help Needed"
    ],
    "post_title": "Follow-up: Windows Server 2025 RDS printing is broken again after 26100.33438 - I’m running out of patience. Half a year later ...",
    "prominence": "aside",
    "source_url": "https://www.reddit.com/r/WindowsServer/comments/1wbmztl/followup_windows_server_2025_rds_printing_is/",
    "entity_role": "vendor",
    "post_author": "xSchizogenie",
    "upvote_ratio": 0.9375,
    "mention_count": 1,
    "mention_surge": false,
    "subreddit_url": "https://www.reddit.com/r/WindowsServer/",
    "total_upvotes": 14,
    "comments_total": 14,
    "total_comments": 14,
    "other_companies": [
      {
        "name": "Microsoft",
        "role": "partner",
        "domain": "microsoft.com"
      },
      {
        "name": "KONICA MINOLTA",
        "role": "alternative",
        "domain": "konicaminolta.us"
      }
    ],
    "post_author_url": "https://www.reddit.com/user/xSchizogenie/",
    "signal_category": "feedback",
    "comments_included": 5,
    "products_mentioned": [
      "Lexmark Universal v2 XL"
    ]
  }
}

curl https://signals.autobound.ai/v1/signals/3d349b85-2631-5b13-a7ec-89bd3db92ec7 \
  -H "X-API-KEY: $AUTOBOUND_API_KEY"

curl -X POST https://signals.autobound.ai/v1/companies/enrich \
  -H "X-API-KEY: $AUTOBOUND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain":"lexmark.com","limit":20}'