🧠 公司知识云

Windows 自 动 登 录 配 置 清 空 密 码 ：net user Administrator "" 注 册 表 HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon 下 设 置 AutoAdminLogon=1、DefaultUsername=Administrator、DefaultPassword…

Windows 自动登录 注册表 netplwiz

Windows 本机搭建私有云 NAS 方案

NAS 私有云 Windows 公网访问 DDNS

问题：在 Windows 上运行 Python 脚本 print 含 emoji（如 ✅ \u2705）时抛出 UnicodeEncodeError: 'gbk' codec can't encode character，exit code 1

方案：Windows 控制台默认 GBK 编码无法输出 emoji/非 GBK 字符。解决方式：1) 把脚本中的 emoji 替换为 ASCII 标记（如 ok / + / -）；2) 或在脚本开头设置 sys.stdout.reconfigure(encoding='utf-8')；3) 或运行时设置环境变量 PYTHONIOENCODING=utf-8。

Python 脚 本 GBK 编 码 报 错 在 Windows 上 运 行 Python 脚 本 print 含 emoji（ 如 ✅ \u2705） 时 抛 出 UnicodeEncodeError: 'gbk' codec can't encode character，exit…

Python Windows 编码 UnicodeEncodeError GBK

问题：Windows下Python脚本print含emoji字符时出现GBK codec编码错误

方案：移除print语句中的emoji字符，或改用纯ASCII/中文输出；根本原因是Windows控制台默认GBK编码无法编码emoji

Windows下Python脚本print含emoji字符时出现GBK codec编码错误 移除print语句中的emoji字符，或改用纯ASCII/中文输出；根本原因是Windows控制台默认GBK编码无法编码emoji [] ["Python", "GBK", "编码错误", "Windows"]

Python GBK 编码错误 Windows

问题：Windows 下运行 Python 脚本打印 ✅ 等 Unicode 符号时抛出 UnicodeEncodeError: 'gbk' codec can't encode character '\u2705'，进程以 exit code 1 退出

方案：避免在 print 中使用 emoji/特殊 Unicode 符号，改用 ASCII 标记（如 + / - / ok）；或显式设置标准输出编码为 UTF-8（如 sys.stdout.reconfigure(encoding='utf-8') 或设置环境变量 PYTHONIOENCODING=utf-8）

Python 脚 本 GBK 编 码 报 错 Windows 下 运 行 Python 脚 本 打 印 ✅ 等 Unicode 符 号 时 抛 出 UnicodeEncodeError: 'gbk' codec can't encode character '\u2705…

Python Windows 编码 UnicodeEncodeError

Windows 本 机 搭 建 私 有 云 NAS 方 案 有 公 网 IPv4 时 无 需 内 网 穿 透 ， 用 免 费 DDNS 域 名 + 路 由 器 端…

NAS 私有云 Windows DDNS 端口映射 Docker

["同时提供三类访问地址：永久公网域名（frpc + chmlfrp 映射）、临时公网 URL（Cloudflare Tunnel 备用）、内网 Tailscale 地址", "首页 banner 展示全部访问地址，方便用户按网络环境选择", "frpc 以守护进程运行，配合 Windows 任务计划实现开机自启", "HTTP 明文传输密码不安全，需 HTTPS 时应绑定自有域名（chmlfrp 支持自定义域名）"] ["frpc", "chmlfrp", "Cloudflare…

frpc chmlfrp Cloudflare Tunnel Tailscale 内网穿透

问题：在中文 Windows 上运行 monitor.py 时，subprocess 的 _readerthread 抛出 UnicodeDecodeError: 'gbk' codec can't decode byte 0xab in position 769: illegal multibyte sequence，导致读取子进程输出失败。

方案：在 subprocess 调用中显式指定编码，避免使用系统默认 GBK：subprocess.run(..., encoding='utf-8', errors='replace')，或传 text=True 时配合 encoding='utf-8'；也可设置环境变量 PYTHONIOENCODING=utf-8 或 chcp 65001 切换控制台代码页。

Python subprocess 读 取 输 出 GBK 解 码 报 错 在 中 文 Windows 上 运 行 monitor.py 时 ，subprocess 的 _readerthread 抛 出 UnicodeDecodeError: 'gbk' codec can't decode…

Python subprocess UnicodeDecodeError GBK Windows

问题：NAS 上存在多个残留的 dsh_watcher 进程和重复的 Windows 任务计划：alice 账号已不存在仍在监听，ehong001 的 watcher 指向 Tailscale 内网地址 100.121.80.122 但本机未装 Tailscale 导致推送失败。

方案：1) 杀掉所有 dsh_watcher 进程（按 PID 逐个 kill，如 9616、11292、3128）；2) 删除旧任务计划（schtasks 删除 NAS-DSH-Watcher-admin、NAS-DSH-Watcher-ehong001 等重复项）；3) 重新启动干净的 ehong001 watcher，--nas-url 指向 http://127.0.0.1:9000；4) 重新安装任务计划；5) 用 monitor.py 验证各服务 running/healthy 状态。

清 理 残 留 dsh_watcher 进 程 与 任 务 计 划 NAS 上 存 在 多 个 残 留 的 dsh_watcher 进 程 和 重 复 的 Windows 任…

Windows 任务计划 进程清理 dsh_watcher NAS

问题：在 Windows 下用 python-pptx 编写 PPT 生成脚本时，多次报 SyntaxError: invalid syntax. Perhaps you forgot a comma?，报错位置均为含中文的字符串行（如 "需要 1"、"增值税和个税联动"等），且终端输出中文乱码。

方案：报错根因是字符串中混用了中文全角引号（“ ”）或未转义的引号，导致 Python 解析器把字符串提前截断。逐处检查报错行号（140、153、589 行），将中文全角引号替换为转义后的半角引号（\"）或改用单引号包裹，确保每个字符串字面量引号成对闭合；修改后重新运行脚本即可通过。终端乱码是 Windows 控制台 GBK 编码问题，不影响脚本执行。

Python 脚 本 中 文 字 符 串 语 法 错 误 在 Windows 下 用 python-pptx 编 写 PPT 生 成 脚 本 时 ， 多 次 报 SyntaxError: invalid syntax…

Python python-pptx SyntaxError 中文编码

问题：在 PowerShell 中调用 .bat 脚本时出现 NativeCommandError，提示 'D:\nas-data\se...ternal command' 不是可运行的程序或批处理文件，exit code 1

方案：不要通过 .bat 间接调用，直接在命令行内联执行 cmd 命令（如 net user、reg add 等），避免批处理路径解析和编码问题

…执 行 cmd 命 令 （ 如 net user、reg add 等 ）， 避 免 批 处 理 路 径 解 析 和 编 码 问 题 PowerShell 批 处 理 Windows 排 错

PowerShell 批处理 Windows 排错

问题：需要给单盘台式机加一块内置硬盘做第二数据盘，用于存放 NAS 数据备份。

方案：选购：西数紫盘 WD10PURZ 1TB 或希捷酷鹰 ST1000VX005 1TB（约 ¥250，7×24 设计），2TB 可选 WD20PURZ；必须选 CMR 垂直式，避开 SMR 叠瓦式和二手/矿盘。安装：关机拔电源并放电 → 开侧板 → 用 4 颗螺丝固定到 3.5 寸硬盘位 → 接 SATA 数据线到主板、SATA 电源线到电源 → 开机在磁盘管理里初始化磁盘选 GPT → 新建简单卷，盘符设为 F:，卷标 NAS-Backup。装好后把备份脚本目标从 D:\nas-data-backup 改为 F:\nas-backup，保留 D 盘一份快速恢复、F 盘一份防盘损，并加每日 03

…定 时 备 份 、zip 完 整 性 校 验 和 磁 盘 空 间 告 警 。 硬 盘 选 购 SATA CMR 备 份 策 略 Windows 磁 盘 管 理

硬盘选购 SATA CMR 备份策略 Windows磁盘管理

…1] MISS C:\Windows\System32\drivers\hvix64.sys MISS C:\Windows\System32\drivers\hvax64.sys MISS C:\Windows\System32\drivers\hvvid.sys MISS C:\Windows\System32\vmcompute.exe MISS C:\Windows\System32…

…1] MISS C:\Windows\System32\drivers\hvix64.sys MISS C:\Windows\System32\drivers\hvax64.sys MISS C:\Windows\System32\drivers\hvvid.sys MISS C:\Windows\System32\vmcompute.exe MISS C:\Windows\System32…

…1] MISS C:\Windows\System32\drivers\hvix64.sys MISS C:\Windows\System32\drivers\hvax64.sys MISS C:\Windows\System32\drivers\hvvid.sys MISS C:\Windows\System32\vmcompute.exe MISS C:\Windows\System32…

…1] MISS C:\Windows\System32\drivers\hvix64.sys MISS C:\Windows\System32\drivers\hvax64.sys MISS C:\Windows\System32\drivers\hvvid.sys MISS C:\Windows\System32\vmcompute.exe MISS C:\Windows\System32…

…1] MISS C:\Windows\System32\drivers\hvix64.sys MISS C:\Windows\System32\drivers\hvax64.sys MISS C:\Windows\System32\drivers\hvvid.sys MISS C:\Windows\System32\vmcompute.exe MISS C:\Windows\System32…

…1] MISS C:\Windows\System32\drivers\hvix64.sys MISS C:\Windows\System32\drivers\hvax64.sys MISS C:\Windows\System32\drivers\hvvid.sys MISS C:\Windows\System32\vmcompute.exe MISS C:\Windows\System32…

…1] MISS C:\Windows\System32\drivers\hvix64.sys MISS C:\Windows\System32\drivers\hvax64.sys MISS C:\Windows\System32\drivers\hvvid.sys MISS C:\Windows\System32\vmcompute.exe MISS C:\Windows\System32…

…1] MISS C:\Windows\System32\drivers\hvix64.sys MISS C:\Windows\System32\drivers\hvax64.sys MISS C:\Windows\System32\drivers\hvvid.sys MISS C:\Windows\System32\vmcompute.exe MISS C:\Windows\System32…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Use the read…

…return 111: } 112: /* v8 ignore next -- POSIX coverage cannot take the Windows peer; native Windows coverage does. */ 113: if (process.platform === 'win32') return 114: /* v8 ignore start -- Windows has no POSIX mode…

…C:\Windows\CSC: IO error for operation on C:\Windows\CSC: 拒 绝 访 问 。 (os error 5) rg: C:\Windows\ServiceProfiles\LocalService\AppData\Local\Microsoft\Ngc: IO error for operation on…

…C:\Windows\CSC: IO error for operation on C:\Windows\CSC: 拒 绝 访 问 。 (os error 5) rg: C:\Windows\ServiceProfiles\LocalService\AppData\Local\Microsoft\Ngc: IO error for operation on…

…On Windows, consider activating Developer Mode to allow non-admin users to create symlinks by following the instructions at https://docs.microsoft.com/en-us/windows/apps/get-started/enable-your-device…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Use the read…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Use the read…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Use the read…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Use the read…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Use the read…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Use the read…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Use the read…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Use the read…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Use the read…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Track every background…

…73: # 检 查 中 文 字 体 （Windows 默 认 有 ，Linux/Mac 需 自 行 安 装 ） 74: ls /c/Windows/Fonts/msyh.ttc # 微 软 雅 黑 Regular 75: ls…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Use the read…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Track every background…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Track every background…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Track every background…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Track every background…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Track every background…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Track every background…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Track every background…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Track every background…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Track every background…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Use the read…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Use the read…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Track every background…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Track every background…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Use the read…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Track every background…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Use the read…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Track every background…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Use the read…

…On Windows a killed process settles as `[exit code: 1]` without a signal marker; treat a bare exit 1 after an interruption as a termination, not a command failure. Use the read…