OSError: [WinError 233] #98307
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#98307
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Win 10 pro 64 bits (10.0 , compilacioon 19044)
Graphics card: GeForce GT 730
Blender Version
Broken: blender 3.1.2
Worked: (optional)
When I was active Rigging: rigify in Blender preferences appears this error at the corner "Python: traceback (most recent call last): File "C:\Program...."
First go to edit
Second Preference
in blender preference selected add-ons
search rigging: rigify and active it
Based on the default startup or an attached .blend file (as simple as possible).
Added subscriber: @luisgustavo5552
Closed as duplicate of #97428
Added subscriber: @rjg
Please check your system for malware. Users have previously reported this error was being raised after their computer has been infected. I've merged this ticket into #97428 where the issue was originally reported.