"Failed to initialize LOOT". Vortex 1.9.12

[thetraveler436]

I received an "Update extensions" notice when I started Vortex this morning. I restarted Vortex as normal and received an error message: "Failed to initialize LOOT".  It appears LOOT is broken for my Steam .1170 Skyrim SE/AE mod order.  I last ran Vortex yesterday and have changed nothing. Here are the details:

Error: libloadorder failed to create a game handle. Details: Failed to parse ini file, error at line 24, column 14: doesn't support inline comment: Libloadorder error
    at l.handleResponse (D:\Vortex\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\index.js:2:619583)
    at D:\Vortex\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\index.js:2:618056
    at Array.forEach (<anonymous>)
    at Socket.<anonymous> (D:\Vortex\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\index.js:2:618039)
    at Socket.emit (node:events:513:28)
    at addChunk (node:internal/streams/readable:324:12)
    at readableAddChunk (node:internal/streams/readable:297:9)
    at Readable.push (node:internal/streams/readable:234:10)
    at Pipe.onStreamRead (node:internal/stream_base_commons:190:23)

 

Edited February 29 by thetraveler436
grammar restructure and corrections

[Pickysaurus]

Not sure if you're the same user as I spoke to on Discord, but this is likely a corrupted Fallout4Custom.ini, delete the file and restart Vortex. 

[thetraveler436]

9 hours ago, Pickysaurus said:

Not sure if you're the same user as I spoke to on Discord, but this is likely a corrupted Fallout4Custom.ini, delete the file and restart Vortex. 

Nope. Not I on Discord. Interestingly, it seems to have resolved itself. The error on start-up is gone although I've changed nothing to fix it. Cheers.